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.
chris_rothermel
OneStream Employee
OneStream EmployeeIrina You mean like having a Source value of "2018M1" and a Target value of "2018M1" where they're both exactly the same?
Dear Chris, yes. I try to find the way to avoid of filling out this mapping for each month, as source and target value are the same.
- chris_rothermel
Thanks for confirming. I have the same issue. The Time dimension doesn't have a mask option, just 1:1 so it appears we're presently stuck with a very boring chore of mapping yyyyMxx to yyyyMxx. I've proposed a solution to bypass this and am awaiting feedback.
Chris, you are correct there is no way around this if you are not using the Workflow time or Global time to drive the period the data is imported to. If you are then my previous feedback holds true as I have many integrations driven by the time taken fro the current Workflow POV and I do not have a Time Transformation Group in my Transformation Profile
