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
Rule Rules - ONLY write rules when necessary.
Rules TIP - ONLY write / use Rules when necessary. OneStream projects should not be a contest to see who is better at writing complex rules. If you must write rules please remember: Unless specified, the calculation will run on Base Entities AND each Parent Entity. Use these lines almost always in your rules. For Base entities only use: If Not api.entity.HasChildren Then For Parent entities only use: If api.entity.HasChildren Then For ALL entities: api.Data.Calculate(“A#Account1 = A#Account2”) There are up to 6 calculation operations in the Consolidation process per Entity. Conditional statements can be added to formulas to limit which Consolidation calculation processes will do something for this formula. For Local currency only: If Api.Cons.IsLocalCurrencyforEntity Then For Translated currency only: If api.Cons.IsForeignCurrencyForEntity Then For Parent-Child Relationship levels: Api.Cons.IsRelationshipLevel returns True for Consolidation level being OwnerPreAdj, Share, Elimination or OwnerPostAdj. For best performance, use Remove Functions – Zero and No Data Can be used in a Member Formula or a Business Rule. RemoveZeros Function removes data cells with cell amount of 0 from data buffer AND removes data cells with cell status of NoData from data buffer. RemoveNoData Function ONLY removes data cells with cell status of NoData from data buffer (data cells in a Data Unit). When declaring variables in a member formula or business rule, ensure the variables are within the calculation conditions to avoid unnecessary code execution. TIP 2 - Don’t Stack api.Data.Calculate Functions. Let's say we need to calculate data for the dimension members below. What shall we do? Use a filter; don’t be afraid to create alternate groupings. Use member filters to perform the same calculation logic for multiple members. Use the hierarchy to drive calculations. Reduces the number of times the Data Unit is called into memory and the number of times data is written back to the Cube. Avoid referencing a user's workflow POV in stored formulas: Finance rules can and often do run outside the workflow. Instead of the above - do the list below. For more information: OneStream Finance Rules and Calculations Handbook. Level 2: Financial Model Rules course.Microsoft Power BI vs. Excel: A Comparison
Power BI is Not Excel 😊 Microsoft Power BI vs. Excel: A Hilariously Technical Showdown Purpose and Functionality: Think of Microsoft Power BI as the flashy superhero of the data world, designed to turn boring numbers into eye-popping, interactive dashboards and reports. It’s the show-off cousin who just got a sports car. Conversely, Excel is the dependable, slightly nerdy sibling who’s been around forever, excelling (pun intended) at data entry, analysis, and complex calculations. The trusty old sedan has seen it all and done it all. Data Handling: Power BI is like a data-hungry beast that devours vast amounts of information from various sources – clouds, databases, and even the web's dark corners. It’s all about real-time munching and crunching. Excel? Well, it's the meticulous librarian of data, handling large datasets with care but getting frazzled if you dump a truckload of info on it simultaneously. It’s great for detailed work, but it prefers its data to be served in manageable portions. Visualization and Reporting: Power BI is the Picasso of data visualization – dragging, dropping, and creating interactive masterpieces that make you go, “Wow!” While competent with charts and graphs, Excel is more like your high school art class. It can make things look good, but it’s not winning any gallery showings. Power BI’s dashboards are so dynamic that they jog when you click on them. Collaboration and Sharing: Power BI is the social butterfly at the party, effortlessly sharing dashboards and reports through Power BI Service, embedding them into apps, and updating them in real time. It’s always up-to-date and ready to mingle on your phone. Excel, bless its heart, tries its best with Office 365 sharing and collaborative editing, but sometimes it feels like sending out invitations via snail mail. Advanced Analytics: Power BI has been hitting the gym with AI and machine learning, flexing its muscles to uncover patterns and predict trends. It even shows off with R and Python integrations. With its powerful functions and add-ins like Power Query and Power Pivot, Excel is like the seasoned chess player – brilliant at what it does but not ready to jump into the AI and ML ring without serious prep. Conclusion: Power BI is the flashy, tech-savvy hero in this epic battle, ideal for real-time visualization, advanced analytics, and collaborative reporting. Excel remains the stalwart, detail-oriented veteran perfect for intricate data analysis and spreadsheet wizardry. Both tools have unique charms and are best used to make your data journey as entertaining and efficient as possible. So, why choose one superhero when you can have the whole team? Coming soon: Power BI OneStream Connector.
