Skip to main content
T
Tommyreebok
Newcomer
July 31, 2024
Solved

Workflow import data overwritten

  • July 31, 2024
  • 2 replies
  • 0 views

we have 2 import steps on our workflow, the main Budget Import and the Fixed Cost Reallocation import.

The main TB is loaded via the budget import and the fixed costs for this TB are loaded to 1 default department.

Later, the entities will reallocate the fixed costs to the correct department via the Fixed Cost reallocation import, the reallocations use the same accounts but a different UD6 to distinguish between the 2 imports. But the original fixed costs amounts loaded via the main Budget import are being overwritten.

Any suggestions to prevent the original fixed cost amounts be overwritten?

we are using separate workflow channels, and we have tried flipping between using True and False on load overlapping sibblings but nothing is working.

thanks

 

 

Best answer by Ioana

I do no think so, but here are the steps followed and you can review them in your app:

1) Assign UD Dimension type to Application Properties in the UD Dimension Type for Workflow Channels  (UD6 in your case). This can be done only for the Default scenario type.

2) Create your channels in the Workflow Channels in the Application tab.

3) Assign the channels to the Import steps. Say channel Budget for the Budget import profile and channel FixedCost for the Fixed Cost reallocation import profile. To note here that you can assign these by scenario type, and it is recommended you only assign the channels to the scenario types you are using them for. In your case, it may be the Budget scenario type. For the other scenario types you may not need to add that extra layer of granularity.

4) Assign the channels to the 2 UD6 members in the Workflow Channels section of Member Properties, again by scenario type. Can leave 'NoDataLock' as Default and only for  Budget Scenario type assign the channels.

5) Assign all accounts as NoDataLock for the scenario type that channels are in use.

6) Can leave 'Load Overlapping Siblings' set to True for the base input profile. 

Thanks.

2 replies

I
Ioana
Newcomer
July 31, 2024

Hello,

There may be an issue on the workflow channels setup that still makes the second profile loaded (Fixed Cost Reallocation import) 'win' over the Budget import. If two import profiles load the same Level 2 Data Unit (e.g. same accounts) the last profile loaded overwrites the first.

Here is a very useful demo on setting up and using workflow channels to incorporate an additional layer of granularity. If set up correctly, the data should be cleared at the UD defined and no other data should be overwritten/cleared/locked.

Using Workflow Channels & Data Type Dimension - October 2023 - OneStream Community (onestreamsoftware.com)

Hope this helps.

    T
    TommyreebokAuthor
    Newcomer
    July 31, 2024

    Hi Ioana,

    Thanks for the reply, Unfortunately the link takes me to a page that says "Access denied". Is this document available elsewhere?

    Thanks

     

    I
    IoanaAnswer
    Newcomer
    July 31, 2024

    I do no think so, but here are the steps followed and you can review them in your app:

    1) Assign UD Dimension type to Application Properties in the UD Dimension Type for Workflow Channels  (UD6 in your case). This can be done only for the Default scenario type.

    2) Create your channels in the Workflow Channels in the Application tab.

    3) Assign the channels to the Import steps. Say channel Budget for the Budget import profile and channel FixedCost for the Fixed Cost reallocation import profile. To note here that you can assign these by scenario type, and it is recommended you only assign the channels to the scenario types you are using them for. In your case, it may be the Budget scenario type. For the other scenario types you may not need to add that extra layer of granularity.

    4) Assign the channels to the 2 UD6 members in the Workflow Channels section of Member Properties, again by scenario type. Can leave 'NoDataLock' as Default and only for  Budget Scenario type assign the channels.

    5) Assign all accounts as NoDataLock for the scenario type that channels are in use.

    6) Can leave 'Load Overlapping Siblings' set to True for the base input profile. 

    Thanks.

      Terms & ConditionsAccessibility statement