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

Keyser_Soze's avatar
Keyser_Soze
Contributor
1 year ago

Attribute Members on Entity Dimension Do Not Translate ?

I'm using attribute members, unfortunately on the entity dimension, so the associated data is stored and not dynamically calculated on Parent Entities.  These attributes members do not translate t...
Consolidation
Cubes
FX Rates
T_Kress's avatar
T_Kress
Icon for OneStream Employee rankOneStream Employee
1 year ago

There are several posts in One Community on how attribute dimensions that are based on the entity dimension work.

Here is one:  Attributes and Aggregation - November 2022 | OneStream Community

And another:  JIRA Ticket: PF-19348

If you do a search in One Community for 'Attribute Entity' you will see many other posts that I think will explain how attributes based on the entity dimension work, considerations, etc.

  • Keyser_Soze's avatar
    Keyser_Soze
    Contributor
    1 year ago

    Thanks for you answer. Prior to writing this post, I've watched the whole video you sent as well as read some articles.
    Maybe I'm mistaken, but I cannot see anywhere the explanation for why 'api.data.calculate()' does not include attributes members even when hardcoded in source formulas whereas data buffers do take them into account (if a property is activated).

    For anybody searching for a way to include attributes members in 'Custom Translations', you need to use buffers. Beware of account types & flow properties ! If you use data buffers, you have to isolate all non-translated accounts such 'Flow, Balance & Non-Financial'.