I have a rather complex SQL query, but I certainly don't believe that the complexity alone is creating the issue that I am now seeing.
What I am seeing is that a previously created, currently functional query works flawlessly as it is written. I have found though that upon creating a new query with the exact same structure I get the following error:
The column prefix 'Nodes' does not match with a table name or alias name used in the query.
I know this issue isn't created by any errors in syntax, because the existing one works perfectly. Even if I go to copy the fully functional query and create a new report with it, the new report gives me the same error. Is something different in Orion causing this issue... or is it just some kind of bug?