We have an issue in one of our Models that is causing us some problems with reporting.
We have a calculated Entity which is using a simple MDX statement Entity1 + Entity2. So Entity=Entity1 + Entity2.
The reason for this is to keep it out of our hierarchy for reporting simplicity, otherwise we would simply make Entity1 and Entity2 children of Entity.
In our Account dimension we have a calculation based on several accounts,but let's say it's Account1/Account2
When we run a report for Entity and the calculated account we either see the result of:
1) (Entity1:Account1/Entity1:Account2)+(Entity2:Account1/Entity2:Account2), which is wrong, but shows the account calculated first and then the calculated entity was solved; or
2) (Entity1:Account1+Entity2:Account1)/Entity1:Account2+Entity2:Account2), which is correct and shows the entity was solved first and then the account was calculated
We have discovered that whichever of the two dimensions is processed last dictates the solve order.
But that's not a good solution, since if someone adds an entity they will invariably forget to process the account dimension afterwards.
I have searched for an answer:
- adding a solve order property in a dimension only works for the calculations in the dimension and this issue is cross-dimensional
- I cannot find a parameter to set in the model or for the environment, but I would think that mostly the account dimension should be solved last.
Does anyone have any suggestion for how to solve this?
We are using BPC 10 MS sp12 and EPM 10 sp16.
Thanks
Chris