Solved
Best practices for handling overlays with varying dimensionality in OneStream
We are designing a planning solution where overlays will be used across accounts with very different levels of dimensionality. For example: Some accounts have minimal dimensionality (straightforwar...
Perhaps using a combination of Constraints and Defaults could get you there. Constraints and Defaults can be found on Entity and UD1. Accounts only use Constraints. Keep in mind that these are assigned by Cube Type.
Or you could get creative and try to use Text fields on members to help guide the user through the UDs. The idea is that the member filters on the form would be read the text fields of the other members. I don't know if this will work but something to think about. If it doesn't work directly with member filters on the form, you could try to use XFBR logic to do it.
Hope those ideas help
