- changed status to resolved
MDX on widget popup table (text box) not taken into account
Issue #354
resolved
See attached image for context. I’m overriding the month on the popup so that if the user selects to comment on Aug, Aug YTD, or Full Year, the comment will always go Aug (based off an attribute on Version).
However entered values still go to the Month element on the row that was selected intially, despite the popup containing the right month. e.g: User selects Full Year row, popup correctly contains Aug, but comment still goes to Full Year. MDX in use below (setting service has same problem).
{ StrToMember( "[Month].[Month].[" + [}ElementAttributes_Version]. ( [Version].[Version].[$<<Consolidation.Version.Version>>] , [}ElementAttributes_Version].[LastActMonth] ) + "]" ) }
{[Month].[Month].[$<<Consolidation.Version.Version::LastActMonth>>]}
2021.07 FP2
Comments (2)
-
-
- removed milestone
Removing milestone: 2021_Q3 (automated comment)
- Log in to comment
Issue has been resolved and the fix will be included in the upcoming November release