sign flip in complex expression
When loading data, all of our accounts from source match the names of the account in OneStream so we've always used a *:* rule for the account maps. However, we have a new dataset coming in and we ne...
Forum Discussion
So, I guess this is the real answer even if it's not a solution. What I need is impossible. How encouraging.
photon nobody said its impossible to handle what you're asking and people have hinted as much already above, for example Jack mentioned derivative rules. There are ways to solve this. If you can't tag the data prior to it hitting OneStream you still have the information that the accounts are revenue accounts in OneStream which you can look up. I think its generally preferred to do this in the transformation stage which you can do here but you also have opportunities to tag or modify data prior to that as well.
I'm not saying it's impossible for OS to eventually arrive at the correct end state, just that it's impossible to do what I asked.
While I appreciate the alternatives proposed by others, they are all bad fits for various reasons.
I'd rather deal with it in source or via some kind of metadata integration than turn a clean *:* rule profile into something that no one in the company but me will ever be able to decipher. The complex expression was a minimal dozen lines of code with built in comments/documentation but it turns out that won't work.
So, I'll figure out another way.
No worries. Another thing you can consider is dynamically building a TR rule. You said you didn't want to manually maintain a rule with 1500 1:1 rules but you don't have to necessarily manually maintain it if you go down this path.
I just recently built something in a project that sucked in some meta-data from SAP4Hana via REST and dynamically built some TR rules for example.
You can also consider lists rather than many individual 1:1 rules when doing this dynamically. In my scenario this was faster.
You know, I so rarely find a use for Lists that I forget about them even when they would be helpful, like this. That's way better than a bunch of 1:1 and I had never considered the performance impact.
Building a dynamic rule seems like a reasonable compromise but I'm punting it back to the source admins before I dump any more time into this.Thanks for the ideas.