m.andrysz |
Posted - 06/26/2024 : 03:17:12 Hi,
We are experiencing some issues with the OLAP reports with two attributes: one is fully expanded, and the second is only on a certain level (Please see the screenshot). It looks like the MDX building engine does not apply nonemptycrossjoin to the second level of hierarchy and does only the asterics intersection.
When trying to replicate an issue in your test environment, we can see that the engine builds similar MDX code but can't observe the same detriment in the report generation.
When we applied nonemptycrossjoin manually to the highlighted similar section on our side, the same report performed much faster.
Is this a bug, and should the MDX builder use nonemptycrossjoin for that section, or is something else wrong on our side?
Regards,
|