Preventing YTD true up for Attribute Member?
Hi, I've set up Attribute Members in my application. They are using Text fields in my UD3 dimension and the Attribute Members are in my UD6 dimension. For default Text values, it works great. Howeve...
Forum Discussion
I have the same situation. has anyone come up with any work around?
The only work around I have found is to use a different account type. I believe that Non-Financial does not do the true up.
We ended up creating a custom calculation that functions similar to an attribute member, but corrects for the YTD true-up issue. Our formula references a manual tag for each member identified from a supplemental import so that it can more easily change over time instead of using the text fields in OneStream.
