Balance Sheet report: displaying two CubeViews in a two-column layout
Hi everyone, I'm building a Balance Sheet report in the Text Editor. For various reasons, I have two separate CubeViews: one for Assets and another for Liabilities & Equity. I've placed both CubeViews inside a table within the Text Editor (one per cell, side by side), trying to display them in the classic balance sheet layout — Assets on the left, Liabilities & Equity on the right. However, I'm having trouble getting them to render correctly next to each other. Has anyone done this before? Is a two-cell table in the Text Editor the right approach, or is there a better/recommended way to place two CubeViews side by side in a single report? Any tips or examples would be greatly appreciated. Thanks!
Entity-Specific Historical FX Rates for Acquisitions — A More Accurate IFRS Translation
Stop Fighting Your Equity Translation — Let HSR Do the Heavy Lifting A 5-minute read for anyone who's ever stared at a CTA movement and whispered: “Where did that come from?” _____________________________________________________________________________ The consolidation problem we all know It’s day 4 of close. Consolidation runs clean. FX looks fine. Then someone opens the equity rollforward. “Why is acquired share capital moving again?” The entity was acquired years ago at a historical acquisition rate, but the system is retranslating equity at current closing FX every month. CTA absorbs the movement. Auditors ask questions. Finance posts manual journals. Everyone loses time. This is the classic Historical Spot Rate (HSR) challenge. The design principle The goal was simple: Freeze selected equity accounts at acquisition FX rates while keeping the standard OneStream Software translation engine intact. No new cube. No custom dimensions. No complicated override framework. Just: metadata tagging, controlled FX logic, and safe fallback behaviour. The HSR pattern Component Design Entity activation Entity.Text5 = "HSR_Entity" Equity tagging Account.Text15 = "HSR_Accounts" Historic rates Stored in dedicated HSR rate technical accounts Translation logic Finance Business Rule Audit trail Dedicated FX movement flow HSR = Historical Spot Rate. The rule only activates when BOTH: The entity is tagged, and The account is tagged. This creates a simple but effective control framework. The historic rate storage design should remain flexible: use technical accounts, use whatever Text property the project governance model agrees on, and confirm all translation account tagging requirements with the Group Reporting Manager before deployment. What does the rule actually do? Check if Entity is HSR_Entity Check if Account is HSR_Accounts Retrieve stored historic rate Calculate FX adjustment Post adjustment to MVMT_TRANS_FX If anything fails → revert to standard FX That last line is important. The design intentionally prioritises: consolidation stability, auditability, and safe fallback behaviour. If metadata is incomplete or a rate is missing, the application simply reverts to standard FX translation logic. No broken consolidations. No blocked close process. Why did this work well in practice? The biggest advantage was operational simplicity. Adding a newly acquired entity became: Load historic rate Apply metadata tags Run consolidation No code changes required. The approach also kept: CTA cleaner, Equity movements are more stable, And audit support is significantly easier. The real challenge: governance The code itself was straightforward. The harder part was operational discipline: Maintaining 1:1 entity-to-rate mapping Controlling metadata tagging Defining fallback expectations Building reconciliation reporting Testing CTA behaviour thoroughly In my experience, most FX translation problems are not technical problems. They are governance problems. Community question I’d be interested to hear how other certified OneStream Software architects and administrators are handling Historical Spot Rate scenarios. Particularly: Are you using metadata-driven activation? How are you storing historic rates? Have you handled HSR entirely through translation override logic? Any alternative designs that further reduce maintenance? How are you handling CTA transparency and audit reporting? Always interested in seeing cleaner or more efficient approaches from the community.
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.Smarter Data Loading: How OneStream Transformation Rules Automatically Handle New Members
In the world of Enterprise Performance Management (EPM), clean and accurate dimensional mapping is essential for a reliable reporting process. Fortunately, OneStream makes this easier through its robust Transformation Rule framework, which intelligently handles new dimension members automatically. Whether it's a new GL account, cost center, or entity, OneStream’s transformation engine ensures that new data doesn’t derail your process, even before user intervention. 🔍 Key Benefits Dynamic Member Detection When a new source member enters the system—say, a newly created account in the ERP—OneStream flags it immediately as “Not Mapped” in the staging area. This provides the user or administrator with a clear indication that attention is required. Mapping can then be quickly added or adjusted to keep data flowing seamlessly. Centralized and Flexible Maintenance Transformation rules support Wildcard and Dynamic Mapping, making it easy to set default routes for unknown members (e.g., directing all new accounts to a placeholder for Unmapped Accounts). From there, consultants or admins can reassign the correct mappings when ready. This approach provides control without interrupting the load process. Built-In Mapping Validation There’s no need to build dashboards or manual reports to detect mapping issues. OneStream’s Data Source and Transformation Rule editors include built-in validation tools to identify unmapped or incorrectly mapped items before they affect results. This enables early detection, faster resolution, and reduces dependence on visual checks. ✅ Why This Matters By leveraging these out-of-the-box capabilities, organizations save time, reduce risk, and streamline their integration workflows. Consultants can focus on higher-value tasks instead of constantly updating mappings, and end users can trust that data loads will highlight issues automatically, before reporting is impacted. Please keep it simple. Do you agree that OneStream handles what it's built to do?
How can I become a Advanced User of Member Filter Builder in QuickView
I am a Financial Planner and Analyst and My Organization use OnStream. I want to understand better how to extract the data for Multiple scenarios (act, fcst, budget, py) using Member filters, variables understand workflows, and parameters?Cube Data Access - pull data to parameter?
Hi, I have an admin dashboard where I show all parameter values and information I need before I start my Data mgmt jobs. There is one value I dont figure out how to show in my dashboard. I have a Conditional input rule on the Cube. Can I create a parameter or Data Adapter or something to be able to pull the value and show in my dashboard? I only need to retrieve the Scenario value.
Metadata Automation
Hi there, I'm looking to automate dimension uploads in that I want the dimension to be "replaced" with the new one that I am loading. I want to reduce the burden of having to add or remove members from dimension and just automate that process. How can this be done and where should I start? Thank you in advance, Joesef
