I recently had an issue using a XREF function that produced the following message:
Error(1024012) Members Destino and PAG_ENT not in same dimension in external reference call
Since I've found few to none information about this error (other that this tread that was not actually related to my problem: @XREF error when using it in calculation), I decided to report my problem and the solution I found.
This XREF function is used in a calcscript to import data from App A to App B, and this calcscript is located under App B —as you have probable guessed.
App A contained two members named "PAY_ENT" (with alias "Entities") and "PAY_IPL" (with alias "IPL").
For another reason not related to this problem, two new members were created in App B and were named "Entities" and "IPL". Although none of the mentioned members was explicitly referenced in the calcscript, the fact of having different members with the same name or alias in externally referenced applications was causing this error to show up (even though the belonged to the "Account" dimension in both applications).
To solve this, I just renamed the members in App B (because renaming them in App B had the less impact) and so I could get the calcscript to work again.
Hope this helps anyone stumbling on this error.
Thanks for posting this up - not too many references to this issue!
The issue seems to have arisen in version 184.108.40.206 - earlier environments do not have the same issue. I would guess that it is to do with the oracle optimisations on the Xref function.
It definitely seems to be a essbase bug, I'm planning to log it to see what response I get.