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.
Simon,
Am I right that you mean column Time on tabs xfd, which are used for loading data in OneStream. Now we indicate Time as the below example:
On tab OS_POV we show the same time member
Yes, Change T#:[2024M12] to T.C# so the Current Workflow time is picked up when you import the data from Excel. You should not need to have a Time transformation group defined with this approach
