If you add a dimension the data should still exist but be stored at the new dimension member level, that is the case for classic and should be the same for EPMA though remembering EPMA doesn't always stick to the rules.
Anyway before adding the dimension why don't you export all the data in column format, then add the dimension, then if required load the data back with a load rule and assign to data to the correct member(s) in the new dimension. Don't forget all the forms, rules etc will be incorrect once a new dimension is added
Thank you, John.
We have also been pondering the possibility of giving a new use to the Version dimension instead of adding a new one, since we are not really using versions (we only manage one version and the users are not interested in having more than one).
What we need is to create the following metrics within the model:
Amount (whichs is Price x Quantity)
Given the particularities of the Version dimension, would you advise to use it as a metrics dimension? Anyway, we understand this implies it won't be possible to keep different versions --or that it will become more tricky. But is there something about model integrity we have to fear if we do so?
FYI, we finally added the dimension. All data was automatically assigned to the root member of the new dimension, so this a something to keep in mind when adding a new dimension to en EPMA planning app.
As this is a DEV application, data is not relevant, but if data was relevant, it's important to anticipate that you will have to treat data before you mistakenly run a consolidation rule -- you can either export then import by using a rule file as you suggested, John, or I guess you can also copy data from the root member to another level 0 member within the new dimension.