Forum Discussion
Solved
Transformation Rules for Time dimension
Hi, all,
Could you please advise why we need to add each base time dimension member on Transformation Rules table when source and target base time member are the same?
Irina, I don't have a super technical explanation for why this is needed—but yeah, it is.đŸ˜ƒ
I usually just create a generic Time Transformation Rule Group to reuse across my Transformation Rule Profiles.
Maybe they added this so you can control which periods are available for loading? Like, to prevent loading into future periods. I know there are other ways to handle that, but this seems like a good fit... even though I've never actually used it for that.
Dear Simon,
If I remove time base member from transformation rules group (for example 2025M1) and load data on period 2025M1 I see below error message (in loaded package time member is the same as in application 2025M1):
Hi Irina,
Perhaps I should have clarified in my original post, if you are setting the time in the Data Source using either of the 2 highlighted options
then you do no need to have Time transformations defined for time in the Transformation Rules Profile. Likely to be the case when loads are performed by the end user using the workflow.