Problem Note 69077: The wrong field names appear in a SAS® Visual Analytics report after you run a Push Monitor to LASR job
After you run the DataFlux® process job push_monitor_to_lasr.djf, you open the Monitor and Dashboard Governance Report in SAS Visual Analytics. You then see incorrect column names on the Triggered values tab. For example, as shown here, a rule is defined on the column MPG_Highway but the field name is displayed as the Invoice column instead:

This problem occurs with tasks that consist of multiple rules. Here is an example that uses five rules in the task properties:

To work around this issue, you must modify the process job by taking these steps:
- Navigate to Extract Data from Repository ► Extract Trigger Values.
- Insert a Data Sorting node between the Keep Exe_ID and Trigger Values nodes.
- Set the fields to sort on the column EXE_ID.
- Add the advanced property NODUPS as True:

- In the data sorting properties, add the RULE_ID and SEQ_ID fields. Then set the fields to sort by EXEC_ID, RULE_ID, and then SEQ_ID:

Operating System and Release Information
| SAS System | Data Management Server | Microsoft® Windows® for x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Enterprise 32-bit | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Enterprise x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Pro 32-bit | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Pro x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Enterprise x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Pro 32-bit | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Pro x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 10 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows 11 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 R2 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 for x64 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 Datacenter | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 R2 Datacenter | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 R2 Std | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 Std | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2016 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2019 | 2.9 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2022 | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Enterprise 32 bit | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Enterprise x64 | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Home Premium 32 bit | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Home Premium x64 | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Professional 32 bit | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Professional x64 | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Ultimate 32 bit | 2.9 | | 9.4 TS1M7 | |
| Windows 7 Ultimate x64 | 2.9 | | 9.4 TS1M7 | |
| 64-bit Enabled AIX | 2.9 | | 9.4 TS1M7 | |
| 64-bit Enabled Solaris | 2.9 | | 9.4 TS1M7 | |
| HP-UX IPF | 2.9 | | 9.4 TS1M7 | |
| Linux for x64 | 2.9 | | 9.4 TS1M7 | |
| Solaris for x64 | 2.9 | | 9.4 TS1M7 | |
*
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.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2022-04-12 09:42:06 |
| Date Created: | 2022-04-12 03:23:00 |