Forum Discussion

aabirached's avatar
aabirached
New Contributor II
7 months ago

UD34, UD56 and UD78 columns in DataRecords

Hello everyone,

While checking a DataRecord table in OneStream Application database, the following three columns exists:  UD34, UD56 and UD78.

Does anybody know what is the utility of these columns?

Is there any method to calculate the value that is added for each of these columns?

Thank you in advance for your help.

Regards,

 

  • Henning's avatar
    Henning
    Valued Contributor II

    Hi,

    The Data Record Tables use a Clustered Index. The columns you mention are part of that index. This is intended for more specific focus on the record tables for processing.

    I am not aware of another use for them other than the index. As for how to calculate the value of each ID in the columns, what would you need that for? I am not sure whether I am actually allowed to share that information. I hope knowing that these columns are used for the Clustered Index suffices ๐Ÿ™‚

  • aabirached's avatar
    aabirached
    New Contributor II

    Hello Henning,

    Thank you for your fast reply ๐Ÿ˜Š

    I am trying to add some data to the data record directly and I was studying the column values to prepare the insert statement.

    Is there any SQL function that helps me add the data without having to calculate these columns (UD34, UD56 and UD78)?

    The same question for the partition ID. I understood that this column is used by OneStreamโ€™s in-memory engines to split up processing by EntityId. Is there a way to know what value I should give to this column?

    Thank you in advance for your help.

    Regards,

     

    • Henning's avatar
      Henning
      Valued Contributor II

      Hi,

      Thanks for getting back to me with your use case!

      Adding data directly to the data tables using SQL is strongly recommended against. This risks system integrity as you only update this table but not all of the related e.g. audit tables. You should always create your data in a business rule, also for instance with the help of SQL and a datatable or dataset, and then save the data in the database using native OneStream functions (Apis).

      Using SQL also risks leaving the solution not supported by the OneStream support if something breaks.

      • aabirached's avatar
        aabirached
        New Contributor II

        Thank you Henning for these information.

        I will check how to do it using a business rule as mentioned.

        Do you have any idea if there is a possibility to add some consolidated data using a business rule without passing by the consolidation process of OneStream?

        Thank you for your help.

        Regards,