Planning: Daily Data to Daily Import to a Monthly App
Have you seen a KB / post that met the requirements for daily data? Please share your experience / practical advice to help us meet daily data requirements. - for Planning - flat files: Daily Data per Month - flat files: Daily Import - Reporting by Day by Month Thank you folks for sharing your expertise.
Process around InUse flag for master data
What do you use as guidelines to flip the "inuse" flag on accounts or entities? Do you wait until the entity balances are brought to zero in your source or some other trigger? What considerations do you make around any immaterial translation values? Interested to hear what your company is doing - thanks so much! -Nicole
Audit tracking: How do you track changes in OS and link with approvals?
Hello! What's your company's way of tracking OS changes and pairing them with approvals? Do you do it manually with a report out of OS that you put in excel and numbered to match the saved approval email in a shared drive? This is how I did it in a previous role where the changes were more manageable :) Do you create a custom database table in OS and add a field to tag to those OS change reports to a ticketing system you're managing outside of OS? Trying to brainstorm a more efficient way that meets auditors expectations but doesn't involve creating a full time role to pair changes with approvals. Any suggestions on how your company accomplishes this would be very much appreciated! Thanks, Nicole
How to Add Adjustments with Add Back Category and Free-Form Add Back Name to Actuals in OneStream?
Hi Everyone, I’m working with Actuals data structured like the attached screenshot and want to add adjustments linked to this data. Key points: Adjustments must tie to Actuals by Company, Account, and Month Each adjustment includes: An Add Back Category An Add Back Name, which is free-form text and can vary monthly I want to maintain monthly detail and enable reporting and drill-down by both Add Back Category and Add Back Name My questions: What’s the best approach to model and load adjustments with both a Add Back Category and a free-form Add Back Name in OneStream? Should Add Back Name be a UD member with auto-create, a text attribute, or something else? How to avoid member explosion or reporting complexity given the free-form nature of Add Back Name? How can I ensure adjustments roll up correctly and maintain data integrity? Any recommendations for validation, governance, and reporting for this kind of adjustment detail? Thanks in advance for your insights!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, can they 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 require runtime computation. Why? 2. Stacked or nested constraints multiply the cost. Does layering constraints across Flows, Accounts, and UDs in OneStream force the system to resolve each filter before executing calculations? 3. Reduced parallelism. When constraints slice across cash flow lines or UD dimensions, the engine can’t fully parallelize tasks. Does more constraint mean fewer threads working freely? Do you agree? Why? CheersArchive 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!
