SYMPTOM:
If users have their metadata upgraded from Strategy 9.3.x to Strategy Analytics Enterprise 9.4.1, they may find these behaviors changed as Strategy Analytics Enterprise 9.4.1 introduces a new feature called “Cube Join” and by default this property as True. Following is one scenario where a difference in behavior is illustrated. When one of the base reports has derived element defined, i.e:
R01 has Category, Subcategory, Item, Revenue, Max(SubCtg@DESC);
R02 has S, Cost, derived element is defined on Subcategory
In document two grids are from the two datasets respectively (shown as the screenshot)
Difference when mapping as transaction input object in transaction configuration.
With Document grids from Multiple Datasets = True, users cannot define Subcategory as Transaction input object in transaction configuration. Following picture compares the behavior between True and False set in this property:
False (Strategy 9.3.x behavior)
True (Strategy Analytics Enterprise 9.4.1 behavior)
CAUSE:
This inconsisteny behavior is introduced by the new Cube Join feature in Strategy Analytics Enterprise 9.4.1.
ACTION:
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release.
WORKAROUND:
If users want the Strategy 9.3.x behavior, the workaround is to disable the Cube Join behavior at project level in Desktop (By default cube join is recommended for Strategy Analytics Enterprise 9.4.1 and higher version).
To do so, Right Mouse Click on the project name >Project Configuration >Project Definition > Advanced > Analytical engine VLDB property configure > Analytical Engine >Document grids from Multiple Datasets >, check the option: Objects in document grids must come from the grid's source dataset only.
45723 KB45723
