A colleague has generated the above error using Enterprise Guide. We're not entirely sure what it means, let alone how to fix it. Can anyone explain what 'scope' means in this context and therefore what might have caused the error?
It's a filter and query node joining several datasets together as a number of left outer joins onto a main dataset. The column name in question exists in other datasets in the query but the error specifies it by TABLE.COLUMN so it knows which one we're looking at. The node contains no calculations, the only changes made to the data are a few column renames e.g. the column in the error is being given an alias in the output of NAME2 (from NAME) to distinguish it from other columns originall with the same name.