Bug or feature: EXISTS() with non-existent first parameter
I just spent a lot of time chasing a mapping table anomaly. The LOAD statement that creates the mapping table used an Exists() to only load mapping values for existing index values. Apparently the field specified as a first parameter didn't even exist and the engine simply creates an empty mapping table. No script error was generated and that message would certainly have helped me in finding my typing mistake a lot sooner...
After thinking a while about this, I could only find one reason why the script engine fails to report an invalid parameter. A LOAD like this one (LOAD DISTINCT alternative) wouldn't be possible because when reading the first row, field A doesn't exist yet.
LOAD A, B, C, D FROM [ExternalFile.qvd] (qvd) WHERE NOT Exists(A);