The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Parser rule to compare attribute data between current month load and last year Dec load
HI Experts,
I have a parser rule that looks at current attribute 9 and compares it with attribute 9 of last year December load and returns it as attribute 10 which helps me map the differences in ...
hi rhankey ,
thank you for your suggestions:
- If this is a direct connect data load, then join in the prior Dec attribute value from source so you no longer need to use a one row at a time parser rule - not a direct connection .Its loaded an an excel csv file.
- Use a Transformation Rule Event handler that performs this particular transformation for all the imported rows in a single SQL statement - does TR event handler have the ability to fetch attribute data for another month (PY dec in this case? )
- If you know the OS api well enough, you could cache a lookup table to OS Global cache. The first time the Parser rule fires would see the lookup table does not exist, and thus create it for all passible values you could need. For all subsequent rows, the parser rule would see the lookup table does exist in Global cache, and get the value from cache - not great with Api's so will have to explore this option a bit more. Any reference will be useful . Thank you.
Yes, you can build a Transformation Rule Event handler to read whatever prior Stage data you want, just as you are doing one row at a time in your Parser Rule. The difference is that you want to issue a single SQL statement to update all the imported rows at one time. Being a Business Rules file, you can do just about anything you want.
I think there are articles in the community showing the basics in how to use Global cache. (Edit) Here is a link that provides a high-level view of Globals:
What is the globals object good for? | OneStream Community
