Hi team,
we are getting a
XQE-PLN-0091 Cross joins (between query subjects: [DatabaseLayer].Dquerysubject, [LogicalLayer].Lquerysubject) are not permitted.
executing a report.
A join exists between Dquerysubject and the underlying querysubject of Lquerysubject at the database layer of the model.
When testing columns from both these querysubjects in the model in FM, the join works fine (no error).
The error is happening on the dev environment, with several reports and different query subjects which are joined in similar way. In production, the same reports and the earlier version of the package still work ok.
As far as we know, there were no changes to these joins between the working and non working version of the model. We are trying to get the model backups to pinpoint the change that could have triggered the issue (it seems it has been going on for a while in dev), but currently just looking if someone has seen a similar problem and perhaps could point to what areas should we check in the model (it's quite large).
UPDATE: Unfortunately Henk's answer did not help, but we were able to narrow down the changed model backup that introduced the problems.
The only area of the changes that should affect these query subjects were inclusions/exclusions in the package. The working model had 14 more database layer query subjects excluded from the package as compared to the non-working model. Once the same query subjects are excluded in the newest version of the model, we are no longer getting the error.
10 of the above mentioned excluded query subjects have a join to either the logical layer object or the underlying db layer object from the error (which is a cost center hierarchy). We are not sure how including query subjects in the package would cause a join to be ignored, but we have a workaround for now.