Blog Post

Blog
1 MIN READ

Tech Talks: Migrating Finance Business Rules to Assemblies replay now available!

jcooley's avatar
jcooley
Icon for OneStream Employee rankOneStream Employee
20 days ago

On this episode of Tech Talks, Terry Ledet joins Tom Linton and Matt Kerslake to demonstrate the process and steps involved with migrating legacy Finance Business Rules into Assemblies while answering common questions along the way! This replay is available here until 10/17/25 so be sure to watch now. You can also watch this replay at anytime on Navigator as part of your Passport subscription.

Tech Talks: Migrating Finance Business Rules to Assemblies

 

Updated 23 days ago
Version 1.0
tech talks
jcooley's avatar
Icon for OneStream Employee rankOneStream Employee
Joined June 21, 2022
View Profile
Blog
Community News, OneStream Updates, and Blogs from Experts

6 Comments

    • jcooley's avatar
      jcooley
      Icon for OneStream Employee rankOneStream Employee
      3 days ago

      Hi, I'm sorry but this link expired on 10/17. The replay is still available on Navigator as part of the Passport subscription though. As a reminder, all Tech Talks replays on OneStream Community are only available for two weeks unless specified in the post. 

  • KH1's avatar
    KH1
    Contributor II
    3 days ago

    Terry tledet​,
    Thank you for sharing your expertise and 3-step formula to migrate the Finance BR to Ws Assemblies.
    Step 1: Service Factory
    Step 2: Service Type: Finance
    Step 3: Standard Class

    Please help me with the below follow-ups as my skill level in OS is low.
    A) Can the Finance BR be migrated in two steps below:
    Step 1: Service Factory
    Step 2: Service Type with defining the functions to be executed: getMemberList(...), etc.

    B.1) If the 2-step formula won't work for the Finance BR:
    - Please share the reasons.

    B.2) If the 2-step formula will work for the Finance BR, please share the benefit of the 3-step formula:
    Step 1: Service Factory
    Step 2: Service Type without defining the functions to be executed: getMemberList(...), etc.
    Step 3: Standard Class with defining the functions to be executed: getMemberList(...), etc.

    C) Please share your leading process to migrate non-Finance BR to Assemblies.
    - I summarized three formulas below:
    1. 1-step formula: Business Rule (Source Code Type)
     - We've used it when moved to v9.
    2. 2-step formula: Service Factory/Service Type
     - We've used it as previously explained by RobbSalzmann​. TY, Robb.
    3. 3-step formula: Service Factory/Service Type/Standard Class
     - Your new tool shared in this TT that we're eager to try for Finance and non-Finance BR.

    Thank you, Terry tledet​.

    • tledet's avatar
      tledet
      Icon for OneStream Employee rankOneStream Employee
      3 days ago

      "Can the Finance BR be migrated in two steps below:" Yes, which would require including the function/method in the assembly file with the service type.  While this can be done, the practice is to have the service factory and service type assembly file, clean and concise "excludes business logic", whereas the class would have the business logic, i.e., method/function.  Developing and maintaining the business logic (method/function) in this manner promotes clean architecture, separation of concern, and provides code that is easier to read and maintain.

      Non-Finance BR to Assemblies can be migrated with the same process, i.e., Step 1: Service Factory, 
      Step 2: Service Type: Finance, and Step 3: Standard Class for the same reasons as migrating Finance BRs to Assemblies.

    • KH1's avatar
      KH1
      Contributor II
      3 days ago

      Terry,
      Please help me with one more follow-up below.
      D) Ws Assembly for       Get       Data Cell - DC/Data       Cell/Dynamic Calcs
      - Please share the benefit of using DC in WsMU v Ws in your demo.
      Thank you, Terry tledet​.

      • tledet's avatar
        tledet
        Icon for OneStream Employee rankOneStream Employee
        3 days ago

        "Please share the benefits of using WsMU v Ws." A WSMU will typically contain code needed specifically for artifacts (Dashboards, buttons, etc.) required for the WSMU; whereas, the code for the WS will be relevant for the entire Workspace.  Developers may also create a WSMU that specifically has code that is relevant for the Workspace and define the Workspace Assembly Service at the WSMU instead of the WS.  WSMU vs WS is similar to a naming convention where some individuals before "param" where others prefer "prm" for a parameter prefix which is to state be consistent and document in the approach whether WS or WSMU is used.