ah ok, my misunderstanding. if you dont want to use it (I dont see any disadvantages to flag it), please be aware if you have some planning levels WITH and some WITHOUT the field, that this could make cross-level calculations a bit more tricky. Check chapter 7.1 "PERIODID and PERIODID(n) Attributes in Time Profile Levels" in the model config guide for more details. Some attribute transformations may need it.
I would have the Time attribute but would not have PERIODID chosen - I would only have the specific PERIODID# fields chosen (i.e. for a technical week planning level, I would have chosen PERIODID1 - 5 (Year, Quarter, Month, Week, Technical Week)).
Selecting PERIOIDID in the planning level is not mandatory. Having said that, if you don't select this attribute in planning level, it will not be possible to use PERIODID in the calculation definition of the key figure defined at the this level.
Thank you for your quick response. So, if I am understanding you correctly, if we just add the PERIODID attribute to each planning level, it wouldn't hurt anything, it would just add possible functionality?
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.