| Aura divider | ||||
|---|---|---|---|---|
|
#883: Trace Calculation Unreadable When Rules are "Large"
#877: Drill on Member for Nested Rows does not Work
#874: Filters periodically don't populate
#873: Filterbar submit button does not work
#867: Cannot save public view as DataAdmin in the cube viewer
#853: Cannot input the sign = in a string cell
#821: Can you remove Column sorting
#814: Default Spreading Prefix: Repeat not working when spread from 0 consolidations
#543: Search box not filtering properly w/ row span
Cube Viewer: Correct value not saved in the mdx after subset update of the global filter
Upload from excel doesn't work correctly with widget filters
Empty view retrieved: issue with the mdx containing "undefined"
#877: Note on updated Syntax for stacking dimensions (with MDX)
As part of the recent bug fixes, a new syntax must be followed when stacking dimensions on rows/columns and defining elements using MDX. The syntax changes ensure that the app correctly handles expand and collapse actions. Here are the key points to consider:
Placeholders for Expand/Collapse Behavior:
When using MDX to define elements and stack dimensions, you must wrap the element definition portion of the MDX within
$<<start>>and$<<end>>placeholders. These placeholders tell the app where expand and collapse actions can occur.Any other MDX outside of the element definition (e.g., filters) can remain outside the placeholders.
Defining Elements Row by Row:
If you are defining elements row by row (i.e., explicitly listing individual combinations of dimension members), in addition to wrapping the element definition with
$<<start>>and$<<end>>, you must wrap the commas separating rows in$<<,>>. This is necessary to ensure that the app processes each row as a distinct combination of members.
Example:
| Code Block |
|---|
{$<<start>>
{[Year].[Year].[2015]} * {[Region].[Region].[World]}$<<,>>
{[Year].[Year].[2016]} * {[Region].[Region].[America]}$<<,>>
{[Year].[Year].[2017]} * {[Region].[Region].[EMEA]}
$<<end>>} |