Announcement
ABC
Recent Activity
OneStream Splash 2026 - Come Meet GES & Spin to Win!
2 MIN READ Today is the first day of OneStream's Splash 2026! Discover the magic of modern finance at OneStream Splash, May 18-20 in Orlando, Florida at the Walt Disney World Swan and Dolphin Resort - bringing together a powerful community of finance leaders ready to Take Finance Further. Packed with inspiring keynotes, over 70 breakout sessions and onsite learning labs, it is a great opportunity to learn and network with other people in the OneStream environment. Are you joining us in Orlando? The OneStream Education Services team will be there, too! Training, Certification, and Community will have space on the expo floor to talk about all things Education Services. Training Come visit the Education Services Training booth to learn about our catalog of instructor-led and on-demand training courses. We’ll be there to answer your training questions and guide you on your OneStream learning journey. Certification Visit the Certification booth to claim your OneStream Certified pins! Have more than one certification? Great- show them all off! Are you just starting your certification journey? Come explore the available exams and learn how to get started! And, enter to win a 30-minute 1:1 exam prep session for the all-new OCS – Financial Close exam with one of the exam’s subject matter experts! Community Stop by the OneStream Community booth to catch a sneak peek of the new Community experience coming this June, learn more about the upcoming “Ask the Expert” event with Jack Lacava, and share your thoughts on the OneStream Community. But wait! There's more. Comment on this Community post providing feedback on Global Education Services training, training experiences, Certifications, the OneStream Community, or the Splash Orlando event and visit the Training booth to SPIN TO WIN! Participants must be in person at the event to spin and redeem prizes. Prizes are limited each day but include Apple AirTags, sweet treats, and even an extra entry for our bigger prize drawings. Hope to see you there!
Assembly in DM Job
Hi OneStream I am trying to add an XFBR from Assembly using the guide ´, and have tried various ways. I tried Current, and even adding the WSMU, and the whole workspace name as well, but to no luck. The data management and the assembly are both in the same workspace/DMU. I believe I am missing the correct way to add the XFBR. Can you please advise what the correct way is? Appreciate it. Thank you.
Registration for Tech Talks: Building OneStream from WinApp to Browser is now open!
1 MIN READ Join Eric Hanson, Tom Linton and Matt Kerslake as they explore bringing a OneStream application created through the Windows App and building it out through the browser! Eric will share tips, insights and guiding principles to optimize your OneStream browser experience! Register now! https://www.onestream.com/events/tech-talks-building-onestream-from-winapp-to-browser/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.
Another user is already logged into the application on this client - Anyone else experiencing this?
Hi OS Community. has anyone encountered this error when logging into OneStream? "Another user is already logged into the application on this client. That user must log out of their external identity provider before you can log in." I ran into this issue today with a user and wanted to see if anyone has experienced the same thing and found a fix. Any help or suggestions would be greatly appreciated. Thank you! Edit: I found a similar post from past [ Unable to Login into OneStream] where it was suggested to log out of the organizational SSO account, but just wondering if there's a permanent fix or root cause of this.The New Community Experience Arrives June 8, 2026
3 MIN READ Mark your calendar! The launch date for the new OneStream Community is now set. On Monday, June 8, the OneStream Community will upgrade to a new platform, providing a new experience for all new and existing users. This move will bring new enhancements and an overall better experience to the Community you know and love. Why are we updating the OneStream Community? Our goal is to empower every member of the OneStream Community with A PLATFORM that enhances connection, accelerates learning, and makes engaging with the community easier and more valuable than ever. The OneStream Community team is committed to ensuring our users always have access to the best possible experience. We’re investing in cutting edge AI capabilities, modern design, and smarter tools—all delivered through a trusted, reliable, and secure platform you can depend on. ENHANCED analytics—paired with new customization capabilities—will allow us to tailor experiences to each member’s needs and surface more relevant, meaningful content. By understanding what matters most to our users, we can continuously refine the community, deliver more targeted value, and ensure every member feels supported, informed, and connected. When is this happening? The launch will happen on June 8, 2026. Starting the week prior, on June 1, 2026 @ 12:00am CT, the current community will be set to read only mode. This means the Community will be TEMPORARILY FROZEN from June 1, 2026 to June 5, 2026 and members will be unable to post new content, post new comments, or otherwise create anything new on the Community. Once the upgrade is complete, members will once again be able to post and engage with the community as usual - but on the all-new platform. Keep an eye on the Community blog for notifications of when the launch is complete. Who is impacted by this? Members of the OneStream Community, including Customers, Partners, and OneStream Employees will all experience this launch and enhanced community experience. Customers, Partners, and Employees who do not yet have an account may create one before or after the launch; however, new accounts cannot be created during the read-only period. How do I gain access to the new Community? The new OneStream Community will remain accessible via the “OneStream Community” button in your OneStream Okta app. Additionally, the new OneStream Community will be housed at a new URL, which will remain largely ungated and visible to Prospects and Guests alike. Details coming soon. How do I stay informed? The OneStream Community team will post notifications when the current community enters read only mode, and again when the new Community is live. Subscribe to the OneStream Community blog today to ensure you receive the latest news and updates from the OneStream Community. Frequently Asked Questions Can I still login to the Community? You can login and use the OneStream Community as usual until June 1. From June 1 through June 5, you will be able to login but you will be unable to interact with the Community until the migration is complete. These interactions include posting new content, liking / upvoting posts, posting replies, joining groups, etc. Will I need to create a new OneStream Community account? No, your OneStream Community account will transfer to the new platform, which includes your username, email address, activity (posts, likes, etc.) as well as your appropriate role, such as Customer, Partner, or Employee. Users who do not yet have a OneStream Community account but would like to sign up may do so prior to June 1 or anytime after the launch on June 8. What will not transfer over? Your rank, profile picture, subscriptions and personal settings will not transfer. Formerly earned badges that exist on the new platform will transfer to the new platform, but any badges that do not exist on the new platform will not carry over. Note: Badges will be assigned following the launch of the new experience. You will receive notifications when your badges have been published to your profile. What do I need to do? When the new platform launches June 8th, simply login via Okta as usual. That's it! More Questions? Comments? Let us know your thoughts in the comments below!
Missing underscore in member names displayed via combo box
Hello! We have a missing underscore in a combo box and I'm not exactly sure why... Here's what shows: Here's how entities are set up: Anyone see this before? Seems related to this one which says it's resolved in 7.1.3 but I'm not seeing that: Underscore in member name not displaying in multiselect listbox | OneStream Community
