You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are multiple levels nested in the row axis definition, only the label of the nested one is displayed in the left upper corner of the LPT pivot:
In this case, the original DeepSee UI displays labels of all the levels:
When there are multiple levels used in a sequence in the row axes definition, only the label of the first one is displayed in the left upper corner of the LPT pivot:
The original DS UI behavior is the same in this case:
I suggest the LPT follows the original DS UI behavior completely by default AND also because the second case is misleading even when displayed by the original DS UI, LPT should provide na option not to display any label at all or to display the pivot/cube name instead.
The text was updated successfully, but these errors were encountered:
Also, when a level member is used in the row axis definition and the members of the lower level in the dimension hierarchy are displayed in the pivot, the lower level label is displayed in the left upper corner of the LPT pivot:
while in the original DeepSee UI, the upper level member label is displayed:
When there are multiple levels nested in the row axis definition, only the label of the nested one is displayed in the left upper corner of the LPT pivot:
In this case, the original DeepSee UI displays labels of all the levels:
When there are multiple levels used in a sequence in the row axes definition, only the label of the first one is displayed in the left upper corner of the LPT pivot:
The original DS UI behavior is the same in this case:
I suggest the LPT follows the original DS UI behavior completely by default AND also because the second case is misleading even when displayed by the original DS UI, LPT should provide na option not to display any label at all or to display the pivot/cube name instead.
The text was updated successfully, but these errors were encountered: