Consolidation percentages bulk load
Hi. I have a lot of changes to consolidation percentages (example : the consolidation % changed in 2024M9 to 60%) to various entities with a time stamp (i.e. history already has default was 100%, then 2023M1 it changed to 80%). However, I cannot just slot the changes into an xml file and load it otherwise it will wipe out the history of the consolidation percentages for those entities and the only info remaining will be the latest change loaded (2024M9 at 60%). Is there a better way to do it than to extract all the ownership information and manually add a new line per entity in the xml extract.How to Run Workspace Assembly from a Data Management Step In 6 Easy Steps
This was originally a question.It took a while to figure out, so to save someone else the hours of trial and error, here is the process I use in detail, start to finish, to run a Workspace-based Data Management step in a Workspace Assembly business rule. Here's a How-to step by step: List of abbreviations used below: DM: Data Management WS: Workspace MU: Maintenance Unit BR: Business Rule AS: Assembly 1. Workspace:Set the NameSpace Prefix - this is what gets filled in at runtime for __WSNameSpacePrefix 2. Assemblies: Note these properties 3. Create the Assembly Business Rule:Create an "Extender" business rule, this is done by right clicking files and selecting "Extensibility Rules" Add some test code, to verify correct configuration, such as BRApi.ErrorLog.LogMessage(si, "Hello from the new extender!"then code the way you would any other extender 4. Create The Data Management Group: Create a DataManagement Group in the same workspace that the Assembly that has your business rule is in 5. Create a Data Management Step - Create a DM step in the new DM Group, reference the rule using the pattern: Workspace.{WorkspacePrefix}.{AssemblyName}.{BusinessRuleName} In this case it would be: Workspace.Current.DMTestAS.DMTestStepExtender Note: we could also use 'DMTestWS' instead of 'Current'.We use Current because the DM Step is in the same WS as the Extender Rule. 7. Done! Test the DM Step with run button and check the error log(System Tab -> Logging -> Error Log),for your test code's output.
How to get two decimal places in Member formula
Hi Everyone, I'm trying to write member formula (not dynamic calc), below is the syntax Dim Var1 as Decimal = Math.Round(api.Data.GetDataCell("A#630000").CellAmount, 2) api.Data.Calculate("A#520000 = A#430000 "*" & Var1 & "). after that getting error "Double is not valid, input string was incorrect format".
Org-by-period
Hi all, Within our application, we have a requirement to be able to do restructurings. This means, on date A, a legal entity is owned by holding A, but on date B, it moves to a different holding company and is then consolidated under that holding company. Has anyone got this working, and if yes, could you share how? What I am running into right now: We can leverage org-by-period settings, but in that case for example opening balances become 0. Plus there is the complexity that you have to set the scenario consolidation view to Periodic, which brings challenges in rolling forward balances where there are no movements. This also means we cannot keep the consolidation setting to standard which means the performance is degrading significantly. So the question is, did anyone get this scenario workign, and can you share how? This would be grately appreciated! With kind regards, Tim Vierhout
Lock Out Sold Entities, Keep Their Impact!
Managing Sold Entities Without Losing Consolidation Results. Hi Community, We’re looking to hear how others handle this in OneStream: When an entity is sold in a specific period (e.g., 2025M5), the requirement is to: ✅ Retain its posted journal values in group consolidation ❌ Prevent any further use of the entity (journals, data loads, forms) The challenge we've encountered is that setting In Use = False — even after journals are posted and consolidation has been run — can cause OneStream to drop that entity’s data from the group during future reconsolidation. This results in the loss of valid P&L impact from the sold entity. Our workaround: Keep In Use = True for the sold period Use workflow locks and security restrictions to block future changes Only set In Use = False once everything is finalized and locked 💡 Feature Suggestion: It would be incredibly useful to have a system property or override flag that allows us to: Set In Use = False to fully disable the entity in the workflow Still retains its consolidated values during reconsolidation How are you managing this today? Your thoughts! Thanks,Consolidation in a Dynamic Cube
Hi Experts, I have a dynamic read only cube, source of this cube is a relational table having details like salary band, department, position, benefits %, tax %, etc. I am simulating some calculations in workspace assembly and setting records in the dynamic read only cube. I see expected data at base entity levels. How can I see correct data at the top entity level? Entity structure: I see same data at multiple levels. Asia and AllRegions data should not be same. Also drill down results are same at multiple levels which is weird. So if we are setting data at base entities in a dynamic cube, how does consolidation work here? JackLacava , would you please clarify this?Disable eliminations and Develop Custom elim
Is there anyway we can develop a custom elimination process in the OS and attached with the cube. I see there is a "Custom" option in the cube properties but dont know what this function will do. FinanceFunctionType.ConsolidateElimination. I developed a custom rules which eliminate at first common parent dummy base member and it all ties when I sum but i wanted to get it roll up to Total Entity in USD.
