Nick,
Thank you for sharing your insight in this post.
Please also share the reasons for using “TotUDx” in a common extensibility configuration.
We are directly using “Top”, no “TotUDx”:
Thank you, NBolinger.
OneStream EmployeeHaving a TotUDx allows you to assign that dimension and collapse the data unit in a summary cube. Lets say in a summary cube you don't need a dimension's detail (customer for example), you can assign the dimension (MainUDx as we call it in the CPM blueprint application) to collapse all that detail down to a single data point - TotUDx so it still consolidates up. If you don't have that TotUDx member, it cannot consolidate up to the parent cube because there is not a proper extension.
