Forum Discussion

NS2025's avatar
NS2025
New Contributor II
2 days ago
Solved

Data loading into BeforeAdj member

Hi All, Apologies if this question has been answered before. I tried search community but couldn't find. I noticed that data can be loaded via Forms into BeforeAdj member. Two questions: ...
Metadata
  • Sergey's avatar
    Sergey
    15 hours ago

    HI NS2025​ ,

    BeforeAdj is a specific Origin member, as a parent of Import and Forms.

    All loaded data will be loaded in the Import origin by default. All keyed in data by the users will be on Forms origin by default as well. BeforeAdj will reflect the aggregation of both loaded and keyed in values by the user, and it will indeed aggregate both Forms and Import members.

    However, BeforeAdj can be used as an input as well in a Cube View, which will allow to override whatever is currently aggregated while placing the offset in the Forms element.

    Example:

    • I loaded 100 euros --> it will be stored under the Import origin
    • I keyed in 10 euros --> it will be stored under the Forms origin
    • BeforeAdj is showing 110 euros
    • I now key in 160 euros on BeforeAdj --> 60 euros will be stored in Forms ( 100 original Import value + 10 original Forms value + 50 as new adjustment into Forms origin)

    Last but not least, any stored calculation can override this behaviour : you can store the output of a calculation in any base member - usually either Import or Forms but any other base Origin member can be used.

Sergey's avatar
Sergey
Icon for OneStream Employee rankOneStream Employee
15 hours ago

HI NS2025​ ,

BeforeAdj is a specific Origin member, as a parent of Import and Forms.

All loaded data will be loaded in the Import origin by default. All keyed in data by the users will be on Forms origin by default as well. BeforeAdj will reflect the aggregation of both loaded and keyed in values by the user, and it will indeed aggregate both Forms and Import members.

However, BeforeAdj can be used as an input as well in a Cube View, which will allow to override whatever is currently aggregated while placing the offset in the Forms element.

Example:

  • I loaded 100 euros --> it will be stored under the Import origin
  • I keyed in 10 euros --> it will be stored under the Forms origin
  • BeforeAdj is showing 110 euros
  • I now key in 160 euros on BeforeAdj --> 60 euros will be stored in Forms ( 100 original Import value + 10 original Forms value + 50 as new adjustment into Forms origin)

Last but not least, any stored calculation can override this behaviour : you can store the output of a calculation in any base member - usually either Import or Forms but any other base Origin member can be used.