@navin.sadarangani.1, this is basically the approach I had adopted, which is basically restating the “Carry Forward From” data in a different form. The two together get us the data we need to get the results we need. I was hoping there’d be a more directly correlated method than this, because this requires an error-prone human not to forget to update two different configurations in the data model (e.g. a time named set having to match the starting month of the version).
All of the workarounds mentioned here are functional, but none of them overcomes the basic problem of having to make sure multiple independent configurations are kept in sync.
I’m building out a company-wide planning model where we will have dozens of this type of thing due to the different types of planning, and making sure all of these different cubes’ configurations are kept in sync, and without the ability to access the starting month as a member property (or some similar method) effectively doubles the number of configuration options and makes every template much more complex than would otherwise be necessary.
It is what it is, unfortunately. I was hoping I was overlooking a way to do this in a more straightforward way, but based on this thread I can see that we’re already on the right track.
Once I get some more of my votes returned, I’ll add this to the UserVoice.