SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 60769: File events are not mapped correctly after importing a flow

DetailsHotfixAboutRate It

After you import a flow with multiple file events, the file events might not be mapped to the correct jobs.

This issue might occur when all of the following conditions are true:

  • The flow is defined with multiple file events.
  • The same file is used for more than one file event.
  • The flow is imported into the metadata.

When you encounter this problem, all logs indicate that the file mappings were correctly mapped. However, when reviewing the flow, you might notice that the file events are not mapped to the correct jobs.

The only workaround is to use the Schedule Manager plug-in to edit the flow in SAS® Management Console, and map the file events to the correct jobs.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Management ConsoleMicrosoft® Windows® for x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8 Enterprise x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8 Pro 32-bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8 Pro x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Enterprise x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Pro x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows 109.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows Server 20089.4_M49.4 TS1M4
Microsoft Windows Server 2008 R29.4_M49.4 TS1M4
Microsoft Windows Server 2008 for x649.4_M49.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 R2 Std9.4_M49.4_M59.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 Std9.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Enterprise 32 bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Enterprise x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Home Premium 32 bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Home Premium x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Professional 32 bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Professional x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Ultimate 32 bit9.4_M49.4_M59.4 TS1M49.4 TS1M5
Windows 7 Ultimate x649.4_M49.4_M59.4 TS1M49.4 TS1M5
64-bit Enabled AIX9.4_M49.4_M59.4 TS1M49.4 TS1M5
64-bit Enabled Solaris9.4_M49.4_M59.4 TS1M49.4 TS1M5
HP-UX IPF9.4_M49.4_M59.4 TS1M49.4 TS1M5
Linux for x649.4_M49.4_M59.4 TS1M49.4 TS1M5
Solaris for x649.4_M49.4_M59.4 TS1M49.4 TS1M5
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.