This is something that used to work as expected in prior releases, but stopped working since v184.108.40.206 that we are aware of.
Steps taken towards issue:
Step 1: add a Source node
Step 2: add a Sort node
Step 3: select a few fields in Sort node to sort with
Step 4: connect a Filter node between the Source and Sort nodes
Step 5: in the Filter node, rename a field used by the Sort node (ie. rename field3 to field3a)
Step 6: open the Sort node
Obs1: In v220.127.116.11 - the field appears red, signifying an invalid field name
Obs2: In v18.104.22.168 - the field is not flagged(highlighted) and looks valid even though it is not.
Obs3: The aggregate node does not have this issue when inserted in this scenario
Step 7: Click Preview
The stream will run and complete in either version, and the log messages warn of the missing field.
Example of log messages after renaming "field3" to "field3a" in the filter node:
Information: Stream execution started
Ignore the invalid field "field3" in the Sort node
Stream execution complete, Elapsed=0.09 sec, CPU=0.05 sec
This seems like something the application should flag as SPSS Modeler does with any other anomaly.
We would like to see this corrected in future releases if possible.
Real Scenario + Problem Statement
|Who would benefit from this IDEA?|
How should it work?
|Geo - Use for OBDR Reporting only|
Why is it useful?
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions