Onestream Certification : Lead architect or Core application architect ?
Hello everyone, I recently attempted to register for a OneStream certification exam and noticed that both the Lead Architect and Core Application Architect certifications are available. Could you please clarify which one is required for my consulting firm to qualify for a higher-level partnership with OneStream? Additionally, I would appreciate any insights into the main differences between these two certifications, as well as the passing score (percentage of correct answers) for each. Finally, if you have already taken one of these exams, I would be grateful if you could share your experience. Thank you in advance!
Can constraints Slow Things Down in OneStream?
Constraints in OneStream are filters applied to metadata dimensions such as Flow, Accounts, UD1, or specific cash flow lines to narrow the scope of calculations, data retrieval, or Cube View rendering. They’re powerful tools, but when applied too broadly or dynamically, they can quietly degrade performance. Larger evaluation footprint A Flow or Account constraint forces OneStream to check every intersection in that dimension. In dense cubes, this can mean millions of evaluations. 1. Dynamic filters are expensive. Static lists (e.g., A#1000, A#2000, Flow#Operating) resolve quickly. Dynamic logic FilterDim, Boolean conditions, or formula-driven sets—requires runtime computation, which is slower. 2. Stacked or nested constraints multiply the cost. Layering constraints across Flow, Accounts, and UD1 means OneStream must resolve each filter before executing calculations, compounding runtime. 3. Reduced parallelism. When constraints slice across cash flow lines or UD dimensions, the engine can’t fully parallelize tasks. More constraint logic means fewer threads working freely. Do you agree? Why? Cheers
Archive applications
Hi all, How do other customers go about archiving applications? We've been live since 2017 and every year after filing our SEC reporting, we copy the production application and rename it with the year that's being archived. This is helpful as in the past we've move products in segments as well as various other master data changes affecting reporting. The issue is that now we're nearing our storage capacity as the size of our application has grown over the years as we add in more data and features (35GB for the 2018 archive while our current 2021 production app is at 155 GB) and clearly this problem will continue every year. Any suggestions on a more efficient and cost-effective strategy? Thanks!
Database space control policies
Hi! We are trying to control the size increase in our production application. We know the growth comes from: Stage tables that allow users to drill down and back onto source data. Data records Audit tables (they can grow a lots if they are recording continuous changes to rules, data for example) Logs which will impact Framework database growth (task activity and error logs, will vary depending on the detail login set in BR, DM and on the system configuration as well as your retention policy) Load transactional data, which will increate your data units and data records unnececarily, which BIBlend should be used for this type of data load instead of loading it to the finance cube. We have analyzed it and we realized the StageAttributeTable and other stage tables has a significant size. Has ayone performed databse maintenance by deleting data from the stage tables? Is it possible to do that while keeping the cube data intact and workflows completed? Any ideas or best practices regarding database maintenance would be very welcome. Regards, Xavi
How do I change a parameter value in a dashboard?
Hi everyone, I have a business rules that is triggered through a dashboard. This Business rule is looking at a True/False parameter. How do I add the parameter to the dashboard and with a dropdown list showing the valid values (true/false) that can be used to save the value to the parameter? Thanks in advance,About Foundation Second Edition
Beyond offering a training guide, the focus of this book is on the ‘why’ of design and building an application. While the foundational principles of building a solid, scalable OneStream application have remained largely unchanged, updates contained in this second edition reflect implemented software enhancements, along with the ongoing development of the OneStream landscape. Manage your Implementation with the OneStream methodology Understand Design and Build concepts Build solutions for the Consolidation of financial data, and develop Planning models Create Data Integration solutions that will feed your models Develop Workflows to guide and manage your End-Users Advance your solutions with Rules and Security Take advantage of detailed Data Reporting using tools such as Analytic Blend and Advanced Excel functionality Tune Performance, and optimize your application New content on Workspaces, Smart Integration, Dashboard design, and more. Over 180 updated images. The information contained within this book is relevant to software version 8.4.0. To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Foreword by Tom Shea Introduction [Peter Fugere, updated by Chul Smith] Methodology and the project [Greg Bankston, updated by Greg Bankston] Design and Build [Peter Fugere, updated by Chul Smith] Consolidation [Eric Osmanski, updated by Nick Bolinger] Planning [Jonathan Golembiewski, updated by Jonathan Golembiewski] Data Integration [John Von Allmen, updated by Joakim Kulan] Workflow [Todd Allen, updated by Chul Smith] Rules and Calculations [Nick Kroppe and Chul Smith, updated by Nick Kroppe and Chul Smith] Security [Jody Di Giovanni, updated by Bobby Doyon] Reporting [Jacqui Slone and Chul Smith, updated by Chul Smith] Excel and Spreadsheet Reporting [Nick Blazosky, updated by Nick Blazosky] Analytic Blend [Andy Moore, Sam Richards, and Terry Shea, updated by Chul Smith] Introduction to the Solution Exchange [Shawn Stalker, updated by Shawn Stalker] Performance Tuning [Jeff Jones and Tony Dimitrie, updated by Jeff Jones]About Planning
Aimed at OneStream Planning practitioners, administrators, implementors, and power users alike, as well as Financial close and consolidations practitioners, OneStream Planning: The Why, How and When is the first standalone book in the performance management space to cover the power and potential of Planning in OneStream. Drawing from real-world deployments, the book is rooted in easily understood business use cases, and explains approaches (with code) through a comprehensive exploration of the solution. All this is offered within a framework of top functional and technical practice as informed by the authors’ decades-long consulting and application development experiences. Which should I do – Import or Direct Load, Consolidate or Aggregate? How do Data Buffers really work; what is Eval and why should I care? Which approach is fastest and does it really matter? Why Multiyear Scenarios should never be Yearly Can Thing Planning run in the Spreadsheet? (It can.) Combining REST API and Analytic Blend Slice Security down to the very tiniest slice Pivot Grid or Large Pivot Grid, that is the question A book filled with clear use cases Exhaustively tested and verified solutions, and extensive source code Undocumented features and functionality covered, along with functional and technical good practices To access the complete publication, you must purchase either the PDF or the physical copy of the book. Purchases can be made at onestreampress.com. Table of Contents Foreword Introduction Chapter 1: Theory, Philosophy, and Practice Chapter 2: Core Planning I – Data and Calculations - Available Excerpt Chapter 3: Core Planning II – Command and Control the Cube Chapter 4: Planning Without Limits Chapter 5: All Data Points Lead to Reporting and Analysis Chapter 6: Specialty Planning Analysis Afterword
