You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Change in Behavior for Duplicate Members Being Returned While Using MDX

in Planning 2 comments

Can someone further explain the upcoming consideration item for 25.08?

what is an "MDX Flow" versus a "non-MDX flow"? Looking to understand use cases where this is going to have an impact.

Starting with the August (25.08) update, the behavior for removing duplicate members for MDX flows will be made consistent with the behavior for removing duplicate members for non-MDX flows.

Currently, certain flows in Planning use MDX expressions such as “Suppress Missing Block” for BSO, “Suppress Missing Rows” for ASO, and “Database suppression” for both ASO and BSO. When MDX is not used, duplicate members are removed from a single row or column definition. In some cases, the duplicate removal in a single row or column definition was silently failing leaving unexpected duplicate members. We are fixing the MDX flow behavior to match the non-MDX behavior which correctly removes duplicates.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!