BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
WWD
Obsidian | Level 7 WWD
Obsidian | Level 7

When using a data-monitoring node, must ALL tables that are to be monitored be pre-defined?  In particular, during the demonstrations, the instructor identified “Customers” and “Employees” as tables that might be analyzed.  When going through the properties wizard for the data-monitoring node, the end-user is required to identify the source table.

 

Let’s say that there was a third table titled “Management” and this table was to be monitored.  Before we used the methodology that was used for “Customers” and “Employees”, would the table “Management” have to be pre-defined outside of the data-monitoring node?

 

Thank you,

 

Bill Donaldson

1 ACCEPTED SOLUTION

Accepted Solutions
Cynthia_sas
SAS Super FREQ
Hi:
The answer is yes. The tables that are available for selection are available via the pre-defined data connections. So all the tables need to be pre-defined.

Cynthia

View solution in original post

2 REPLIES 2
Cynthia_sas
SAS Super FREQ
Hi, Bill:
Asking the course instructors.
Cynthia
Cynthia_sas
SAS Super FREQ
Hi:
The answer is yes. The tables that are available for selection are available via the pre-defined data connections. So all the tables need to be pre-defined.

Cynthia