Skip to main content
N
NS2025
November 13, 2025
Question

Automatic update of Metadata in OneStream?

  • November 13, 2025
  • 4 replies
  • 5 views

Does it make sense to get OneStream Metadata (eg Entity, Cost Center etc) be updated automatically from upstream source system such as SAP?

I would have thought it would be far too risky but just want to check if anyone out there had ever come across such requirement and what approach you deploy so that metadata between source ERP and OneStream are in sync?

Thanks in advance for sharing your experience.

    4 replies

    T
    T_Kress
    November 13, 2025

    There is a OneStream Solution Exchange tool called Application Control Manager that handles metadata integration between source systems and OS.  

     

    M
    MikeG
    November 13, 2025

    Hi NS2025​ , the only dimension I would stay away from automating is the Entity dimension.  Entities drive Workflows and Security.  If your application has Intercompany and FX translation requirements, that adds to the complexity of auto-adding new Entity members.  T_Kress​ beat me to it, the ACM is your best bet.  I'd just recommend re-thinking how you want to manage the Entity dimension automation.

    Regards,

    Mike G

    N
    NS2025Author
    November 14, 2025

    Hi T_Kress​ & MikeG​ - thanks for your responses - much appreciated. Very helpful.

    What the user wants is straight-through automated processing of metadata without any human invervention from the source system (SAP) into OneStream.  I just wanted to confirm that although it is doable (for e.g. using APIs) - it is something thta one shouldn't do given the complexity of the application. ACM makes lot of sense - I will explore that.

    A
    anna_ivinska
    November 14, 2025

    Hi NS2025​ 

    In our company we have fully automated Entity update from an external MAster ORG tool/db. But all logic to identify change is built outside OneStream. (or, it is possible to bult it in new tables within Onestream as well).

    The principle is: 

    1. make 2 snapshots of ORG : one from Onestream previous period, another - from ORG master - latest period
    2. compare snapshots to find delta - NEW, Changes (various fields), MOVEMENTS (in hierarchy)
    3. populate changes into own tables
    4. create xml files based on tables
    5. put files on sftp
    6. trigger powershell script on Azure - log into Onestream and initiate Data Management job "get files from sftp". Business rule with connection to SFTP does already exist in Onestreram (extensibility rule)

    We are using several systems for full automation.

    N
    NS2025Author
    November 15, 2025

    Hi anna_ivinska​ - that's very interesting indeed.

    Two questions:

    (1) What is ORG that you are referring to? Do you mean entity structure in your environment?

    (2) Are you using any text variables in your entity dimension that drives consol, workflow, calc or reporting behaviour?  If so, how do you ensure that correct text variables are deployed in OneStream entity structure?

    Thanks for sharing!

    A
    anna_ivinska
    November 18, 2025

    (1) Yes, it is our own ORganisation (Entity) master tool. But it could be any other system - tables within SAP or other.. The thing is that you need tables - in your case in SAP - that contain all information about Entity structure. So, after greenflag from source system - Entity tables with status-quo /snapshot are copied to some db where you also have Entity snapshot from Onestream for previous period. We do export Entity dimension from Onestream as XML, put it on SFTP. We use IICS - Informatica system for ETL - unpack XML, put content to tables. Then runs several SQLs to compare tables to find delta.

    So, a lot of processes are done by Informatica. But you can investigate Power platform - Power Automate - (parse XML; SQL connection). Could happen that pack / unpack XML could be doable by PowerAutomate. PowerAutomate has SQL, SFTP connections - so full automation probably could be achieved by using  this product.

    Here are steps within DataManagement sequence that is being triggered from logic app on Azure (advanced PowerAutomate) . As you can see, we create XML files with security groups, WFs, 2 Entity dimensions, update Transformation rules

    (2) in order to keep values from text attributes, you need to have 2 tables - one with latest snapshot, another - with historical values. 

     

    Terms & ConditionsAccessibility statement