Product Support and Maintenance Policy
OneStream is committed to continually developing and enhancing our SaaS offering and software, providing customers with innovative solutions to meet ever-growing requirements. As new versions are introduced, OneStream actively plans to retire older versions. To support this, OneStream has implemented a Product Support and Maintenance Policy which is available at: https://www.onestream.com/saas-terms-and-conditions. As per the Product Support and Maintenance Policy and the terms, General Support ends 30 months after release. In 2025, this policy will be further implemented by giving customers the option to upgrade to the latest version or transitioning customers on unsupported versions to a prepaid support model. When a customer upgrades to a supported version, General Support will continue to be provided as per the Product Support and Maintenance policy. Prepaid Support Prepaid support is a 6-month contract that is available after General Support ends as a bridge to a supported version. To request this, log into ServiceNow and under the Software Customer Service Catalog, choose Other and then select Customer Statement of Work. Here you will complete a request form for End of General Support. Support During Upgrades Customers with an active Upgrade Case (Software Upgrade, Cloud Migration Readiness, and Cloud Migration) will be provided with support for a period of 3 months during the upgrade. Upgrade Cases will continue to be available after General Support and prepaid support end. Informational Banners To ensure our customers are aware of their upcoming End of General Support date, we have released informational banners in the Support portal. They will appear 6 months before the End of Support date. The banner will contain a countdown of months remaining before End of General Support. ‘0 months remaining’ means thatGeneral Support will end on the 1 st of the next month. After this, a new banner will appear explaining that General Support has now ended, and that an upgrade is required. Customers on older contracts may see an End of Support banner without a specific date or a countdown of months remaining. In this case, the End of General Support enforcement will begin at contract renewal. For customers actively upgrading, the banner may disappear. If the upgrade becomes blocked due to lack of response or significant planned delay, the banner may re-appear. FAQ How can I tell what my End of General Support date is? For most, the End of General Support date is 30 months after the release date of that version. To locate your release date, review our Release Notes. Navigate to documentation.onestream.com -> release notes -> Platform -> End of Support Dates For customers who are on versions that are already out of General Support, upgrade dates are in staggered batches based on release dates and contract terms. These customers will receive a banner with a specific date or a countdown towards that date. Lastly, for some customers on older contract terms, the Product Support and Maintenance Policy will apply from contract renewal. They will receive a banner without a date or countdown. How are release dates calculated? The Product Support and Maintenance Policy establishes End of Support dates from the major and minor versions. Hotfixes do not reset End of Support dates. For example, the End of Support date calculation for all v7.4.x versions is based on the release date of v7.4.0. My End of General Support date is coming up, but I need more time to upgrade. What are my options? You may submit a Software Upgrade for v8+ to begin a 3 month grace period. You may also purchase Prepaid Support for 6 months after your End of General Support date. My version is already older than 30 months. Will I lose access to the Support portal immediately? We have staggered upgrade dates based on your release date. There will be an informational banner in the Support portal to advise on your End of Support date. If you do not see a specific date, General Support will end at your contract renewal. Can I purchase prepaid support before my End of General Support date? Yes. From August 1 2025 it will be made available to customers before their End of General Support date, and up to 6 months thereafter. I have an existing balance of OneStream Support hours on my CSRS OnePass Subscription. Can I use those hours after End of General Support? Yes. If you have a balance of purchased hours on your CSRS OnePass Subscription, those hours can still be used when General Support ends for a maximum of 6 months. Where can I find the full Product Support and Maintenance Policy? https://www.onestream.com/saas-terms-and-conditions, then look for ‘Product Support and Maintenance Policy.’1.2KViews0likes2CommentsExtensibility Series: Riding the Wave of Vertical Extensibility
What is Vertical Extensibility? Vertical or entity/cube extensibility is the transformative feature of OneStream’s Extensible Dimensionality that allows for the collapsing and extension of dimensional detail as you move up and down the entity hierarchy. This feature offers the ability to include and/or exclude detail at different levels in the entity structure, and its proper use has three major benefits: It allows for a single, unified, data model to provide the flexibility required in management reporting while maintaining a single source of truth. It allows for the management of data unit sizing to provide a highly performant end user experience. It provides flexibility and future-proofing by setting the foundation for growth in your business and the OneStream platform. Instead of needing separate, distinct, data sets to meet the various reporting needs of your business, vertical extensibility provides the ability to maintain a single linked data model. The cube structure and data model in OneStream is flexible enough to include the details where they are needed and exclude them where they are not (while still providing visibility through drill down). The main difference between horizontal and vertical extensibility is that horizontal is within the same cube across different Scenario Types while vertical extensibility is across cubes in the same Scenario Type. A common example of vertical extensibility showcasing all three of the benefits mentioned above is that of a Summary cube (sometimes referred to as a “super-cube”) containing a total company entity and various Detail cubes (or “sub-cubes”) for each of the various business units in that company. In the CPM Blueprint application, you can see this type of configuration within the FinRptg linked cube structure as diagramed below. In this example, the cubes and data models are linked through a common entity hierarchy. When we look at the entity dimension above, it’s not immediately apparent that anything is going on there. However, when we compare the cube dimension assignments for Actuals, you can start to see differences in the level of detail. In the FinRptg cube, we can see that a summary level of Accounts, UD1, and UD2 have been assigned. This will allow us to collapse the data unit down to that more summary level used in total company reporting. In the account dimension, for example, the lowest base members in the FinRptg cube would be at the NetRev, COGS, and OpEx level. When data consolidates from an entity in a sub-cube to a parent entity in the FinRptg cube, the records will be collapsed and stored in the higher dimensionality members. The lower-level base entities (ex. BU_100) and BU parent entities (ex. TotBU1) that exist in the FinBU1 and FinBU2 cubes will still have the more detailed granularity, but the TotCORP entity will only be stored in the database at that higher level. Without vertical extensibility, every distinct base intersection from both detailed cubes would also be stored for TotCORP as shown below: Applying vertical extensibility to our design allows us to collapse the data unit as it moves into the summary cube. This allows us to better manage the data unit size and keep the details where they are reported on. Applying this concept to the database records we looked at in the previous example, you can see a considerable reduction in the TotCorp entity data unit size and the amount of data we are storing in the database: Base revenue accounts collapsed into NetRev. Base geographies collapsed into a summary level (NA / EMEA). Base products collapsed into a summary product line (Product Line 1 / Product Line 2). The benefit of this is a direct reduction of the TotCORP entity’s data unit size which will lead to more snappy reporting and improved consolidation times. With the linked cube structure, we can directly drill down from TotCORP at the higher level into either TotBU1 or TotBU2 which sit in the detail cubes whenever we need to explore additional detail. Looking back at the CPM Blueprint application’s cube dimension assignment, we can also see a different application of vertical extensibility in UD3. FinBU1 does not collapse detail into FinRptg (as they both have the ProductSummary dimension assigned) but FinBU2 does. This shows the ability to vary base dimensions in each of the detail cubes. Perhaps different business units across the company use distinct cost centers, separate charts of accounts, or in this case, BU 1 may have a more detailed breakout of products than BU 2. This use of vertical extensibility allows the cubes to be more targeted to the data. This will improve the performance and end user experience by reducing sparseness. With this configuration, we can exclude members that aren’t applicable to BU 2. When designing an application, it’s important to consider future flexibility and expansion both within the business and the OneStream platform. Utilizing vertical extensibility to configure a linked cube design from the start leaves the door open by providing numerous possibilities in the future. By extending the entity dimension down from a summary cube to at least one detailed cube, you are then able to: Expand and collapse detail in separate scenario types as they consolidate up. Utilize vertical extensibility on any new dimensions activated in the future. Link additional detail cubes to the summary cube. Once Workflows have been configured and data has been loaded to a cube, you cannot add a summary cube above it. The foundation has been set and your options around flexibility and managing the data unit size have been truncated. How Should Vertical Extensibility be Applied? Vertical extensibility is the natural next step in the extensibility design process. After aligning on the levels of input each dimension should have, you should also discuss how the detail varies across business segments and what levels of detail are required for reporting. In design I find myself asking some of the following questions: Do all entities follow the same chart of accounts? Do all entities follow a similar breakout of detail (geography, products, cost center, etc.)? Are there common characteristics of entity groupings? How does corporate reporting differ from management and base entity reporting? At a consolidated level, do you need to see the lowest level of detail? The most granular GL accounts? Each individual product? Every project? Could a restructuring cause entities to move between BUs or other groupings? Planning & Preparation In terms of order, I like to start with horizontal extensibility first. Horizontal extensibility is more of a business process mapping into OneStream while vertical extensibility is more of a technical lever to drive performance, maintenance, and flexibility. Because of this, I find horizontal extensibility to be easier to understand, and I like to let the client walk before we run. I suggest having the business define input extensibility across scenario types first and then work into the reporting levels and variances across business units or other groupings. I find this exercise to be a back-and-forth refining process. Look at existing reports, analyze what needs to be produced out of OneStream, and make suggestions on the details in each cube. Solicit feedback and refine the suggestions. Bump up calculations that need to run, ad-hoc reporting, etc. to the suggestions and further refine. And finally, map out the combined vertical & horizontal extensibility in a matrix that the business can visualize and agree upon: Throughout this design process, it is helpful to mockup what the data will look like in OneStream and what will/will not be valid with this data model: Remember that alternate entity hierarchies will also need to be extended from summary into the detail cube(s). All entity structures (ex. Total Legal, Total Management, Total Tax, etc.) need to be thoughtfully planned out to incorporate extensibility and alternate entity parents placed in the proper cube. If possible and time permits, create a quick strawman and load some raw data in a OneStream application so the client can play around with it and visualize in QuickViews and drill downs. This will help further their understanding and learning journey. To reiterate, this is the time to set a healthy foundation for the future. Configuration The configuration of vertical extensibility and the linked cube structure has three main pieces: Configure the entity dimensions. Create the cubes and assign the created entity dimensions. Assign the cube references. Configuring the entity dimensions Continuing with the example in the CPM Blueprint application, we will need to configure three entity dimensions and link them by adding cross-dimensional relationships. First, we create the three entity dimensions and the desired members within each: Next, we need to add relationships to link the structure. Select the FinRptg entity dimension, click on the TotCORP entity, and follow the steps in the image below: Select “Add Relationship for Selected Member” TotCORP should be populated as the Parent Member. Select the ellipsis to the right of Child Member. Change the dimension from FinRptg to FinBU1. Select the TotBU1 entity. Select OK on the “Select Member” popup window. Select OK on the “Add Relationship” popup window. Repeat process for adding the TotBU2 entity relationship. After assigning these relationships, you will see the full linked structure in the FinRptg entity dimension. Note: The entities in black text are members of the FinRptg dimension while the entities in gray text are inherited members. Create the cubes and assign the created entity dimensions The next step is to create the cubes and assign the configured entity dimensions. Continuing with the CPM Blueprint application example, we will need to configure three cubes (FinBU1, FinBU2, & FinRptg) More information on proper cube dimension assignment can be found in the linked article. Assign the cube references The final step is configuring the cube dimensions and assigning the proper cube references to link them. Select the FinRptg cube and navigate to the “Cube References” tab. It will auto-populate based on the entity dimensions linked previously but the cube references also need to be assigned to complete the cube linking. After configuring extensibility and assigning the proper Cube References, the Cube Properties and Data Access settings may also need to be updated: Is Top Level Cube For Workflow should be set to “True” on the summary cube. Workflow suffixes should be set on the summary cube. This section will be grayed out on all linked detail cubes. Calculation settings typically align across the linked cube structure. Business Rules that need to be run in all cubes (ex. Custom Translation) should be assigned in both the summary and the linked detail cubes. Data cell security settings may need to be maintained in all cubes depending on the requirements around them (ex. UD1#200 requires data cell access security and UD1#200 exists in all cubes. Therefore, the data cell access “slice” security must be applied on all cubes in the linked structure). Recommendations & Considerations The Data Unit is a key concept to understand in OneStream. It is important to effectively manage its size to allow for optimal performance while accounting for future growth. Vertical extensibility directly affects the data unit size as you consolidate up the entity hierarchy by allowing you to vary the levels of detail assigned across business units and summary levels of the business. The mindset going into an application design should not be whether or not to use vertical extensibility but rather how it should be applied. There are very few cases where vertical extensibility should not be used because of the benefits outlined in this article. Even in cases where the same dimensions are assigned to both the summary and detailed cubes (therefore not collapsing the data unit at all), I would still utilize a linked cube structure. This foundational setup allows you to use a separate Scenario Type in the future if the data unit size or performance does become an issue as the business grows or new use-cases are brought into OneStream. When deciding how many detail cubes to include in an application design, it is important to weigh many different factors including: Are there data unit size concerns with a single detailed cube? Having a consolidated member across various BUs within a detailed cube could lead to an unmanageable data unit depending on the use of UDs and data volume. Is there a business reason to split into separate detail cubes? Maybe they have different charts of accounts or other dimensional differences (ex. Services vs Manufacturing). How often do entities move between business units? Frequent movements would be complicated between cubes so you may want to contain these in a single detail cube. However, if it’s once every three years or if you have to stretch to remember the last time it happened, the benefits may outweigh any effort to (potentially) move an entity between cubes later. What is shared across business units or other management structures vs what is distinct? If most items are shared, does it make sense to split across cubes? Consider any potential business changes as well if they may push these business units to be more aligned in the future. How do internal controls differ? How should we be thinking about cubes in relation to the security model? Applying extensibility is a balancing act. Too many dimensions and cubes can add maintenance overhead and detract from the end user experience. Too few can slow performance and also detract from the end user experience. There are typically compromises across the business during design. For example, it may make more sense to add a few accounts to a common chart to be able to share across the business, or to add some product lines to a business unit’s dimensionality even if they don’t use them. Instead of splitting these entities out into their own cubes, the complexities may outweigh the benefits. In design, it is important to outline the assumptions and reasoning behind a particular decision. List the options that were considered and the reasons they did not prove to be the best fit. With so many design levers at our disposal, it is helpful to have callbacks to the conversations that were had leading up to the final documented design. In a linked cube structure, reports in OneStream can be created using the parent cube. The concept of Merged Hierarchies allows OneStream to understand the extended entity’s data model from within the parent cube. Use “MergeMembersFromReferencedCubes” to control the extensibility level in reports. Example: A#IncomeStatement.TreeDescendantsInclusive.Options(Cube = |WFCube|, ScenarioType = XFMemberProperty(DimType=Scenario, Member=|WFScenario|, Property=ScenarioType), MergeMembersFromReferencedCubes = False) Finally, as detailed in the horizontal extensibility article, it is important to properly configure account-type dimension extensibility or else it will not consolidate up to the summary cube in a linked cube structure. When reconciling data in a detailed cube, this issue won’t present itself but when the data tries to consolidate up to a parent entity in the summary cube, it doesn’t have anywhere to go if you have not extended from a base member. For the most part, this consideration should apply to all configured dimensions but there are select use cases where it is desirable for the data not to consolidate up to the summary cube and those members not be visible to other business segments. Some examples of this include drivers specific to a business unit, dynamic calculations specific to one segment, and alternate hierarchies specific to one cube. Conclusion Vertical extensibility allows OneStream to remain a single source of truth for both corporate and management reporting. By extending dimensions down the entity hierarchy, organizations can avoid fragmented systems and empower users with the detail they need. Proper application of vertical extensibility provides: Performance benefits Flexibility to assign dimensional detail in a more purposeful way Future-proofing by leaving the door open to additional configuration options Lower maintenance overhead with a single unified data model Extensibility should be a discussion topic in every solution design. Its use is the key to unlocking the full potential of the OneStream platform.95Views2likes0CommentsSeptember 2025 Customer Newsletter
This month we're announcing updates to the Financial Close and ESG solutions, helping you save on Instructor-Led Training courses and certification exams, sharing how Parkdale Mills eliminated manual reporting across seven spreadsheet consolidations, and so much more! View Newsletter The September 2025 OneStream customer newsletter includes: Product Updates - OneStream Financial Close and ESG Connect North America - Events in Minneapolis, NYC, and Atlanta Education - New and updated courses, training special offer and more Customer Story - Parkdale Mills streamlines reporting and close cycle Solution Exchange Spotlight - Workforce planning with CompAnalytics OneStream Solution Spotlight - SensibleAI™ Studio Upcoming Events, Webinars and User Group Meetings Report - Women in Finance58Views0likes0CommentsExtensibility Series: An Overview of Extensibility in OneStream
What is Extensibility? The concept of Extensibility in OneStream is the capability to incorporate multiple use cases and future growth with a single foundation. I like to relate this to a dinner table that can expand and add additional table leaves while maintaining the same integrity. The OneStream platform, in tandem with Workflow and Extensible Dimensionality expands on this concept by providing users with multiple ways to extend their platform footprint. When designing an application or planning for expansion to the existing footprint, these concepts are crucial to understand and apply correctly. Extensibility in OneStream is a broad topic and can mean something different to each person in the community so I would like to break our language on this topic down further into the following categories: Horizontal Extensibility Vertical Extensibility Workflow Extensibility Platform Extensibility Horizontal or Scenario extensibility relates to the ability to extend and use different levels of a hierarchy for different business purposes. It also provides the ability to target when and where dimensions need to be included in the data model. Have you ever wanted to input data at a parent level? Through horizontal extensibility, that parent can become a base for input in a different scenario by using the scenario type settings and properly applying Cube Dimension Assignments. What if you have highly detailed metadata that only applies to a specific use case? Horizontal extensibility can help limit the potential intersections that aren’t valid for all the other use cases by assigning it only where it makes sense. Vertical or Entity/Cube extensibility relates to the ability to include/exclude detail at different levels up the entity hierarchy. The Data Unit is a key concept to understand in OneStream and it is important to properly manage its size to allow for optimal performance while accounting for future growth. Vertical extensibility also relates to varying dimensionality across business units. When you report consolidated financials, do you need to see the lowest level of department detail? Each individual product? Every project? The most granular GL accounts? If the answer is no to any of these, vertical extensibility can help. Lower-level entities can still report at a detailed level, but the data can be collapsed to a summary level to facilitate the reporting and increase performance. Does your organization have Business Units with very different operations? Perhaps vertical extensibility can provide the flexibility you need to vary the dimensionality at a detailed level but consolidate to a common summary level. Workflow extensibility relates to the ability to vary the input steps & methods within each process flow. Workflow steps and settings can be adjusted on each scenario type or can be combined if multiple processes follow the same responsibility hierarchy. Workflow extensibility can be configured on each parent cube to tailor the software interface to match the process needs. Is your Actual data collection process more import driven and the Planning process more forms, calculations, and dashboard driven? Workflow extensibility can help split these processes and make them easier to manage from an administration standpoint. Are some data collections imported in a centralized fashion while others have their responsibility distributed to more end users? Entities can only be assigned once in a Workflow hierarchy so to vary the entity signoff responsibilities, Workflow extensibility should be utilized to allow for differing entity assignments. Platform extensibility relates to the ability to vary where data is stored and how it is utilized within the platform. It also includes the ability to have multiple applications within one environment that can talk to each other. OneStream has the unique ability to consume, utilize, and report on data regardless of if it is stored in cubes, relational tables, or even externally. The capabilities in this category are expanding rapidly and should be considered during all solution design activities. Do you plan at a named personnel level? By each individual capital project? It’s important to determine what is necessary in the cube for consolidated reporting versus what can live outside the cube to be reported on more at a base entity level. Through platform extensibility, we can combine cube data with relational data to achieve the optimal balance between performance and reporting needs. Is the process you are designing more operationally driven and your data dimensions more transient in nature? Perhaps none of a specific data set needs to live in a cube, or even OneStream at all. Platform extensibility allows us to utilize entirely relational data, web content, and even external data sets. How should one think about Extensibility? Extensibility is foundational to OneStream. It should be thought of as a tool as essential as the level. Without it, you can probably get the job done and, on the surface, it might look okay as well. But over time, you are likely to discover structural integrity issues. It is probable that what you built may no longer be able to do everything you need it to. We use extensibility to right-size data units. We use extensibility to input at the right level. We use extensibility to fit the business process. We use extensibility to set the foundation for the future. I’ve heard people talk about extensibility in that you are “locked in” to the choices you make now. While there is some truth in that, it should not be thought about as a box, but a key to the future. Applying extensibility opens the door to so many more options in the future. Design the process and use extensibility as the tool to bring it all together. As mentioned in the Guiding Principles article, the importance of designing the process cannot be stressed enough. Don’t look for a tool, look for a problem and use the tools provided. Be forward thinking during design and ask questions to all stakeholders to make sure future functionality is accommodated for. Be sure to understand how the business operates and what is on the roadmap so that the proper foundation can be built. Recommendations I will begin with a disclaimer, there is not a single be-all, end-all way to implement extensibility in OneStream. I have seen applications with no extensibility and ones with too much extensibility. While there is a middle ground that should be found, the applications without extensibility are those that much more commonly have issues. A lack of vertical and platform extensibility tends to lead to performance issues. A lack of horizontal and Workflow extensibility tends to lead to flexibility issues. The applications with too much extensibility less commonly run into performance or flexibility issues, but they do have a higher maintenance burden. This is why, as architects, it is our job to balance performance, usability, and maintenance when thinking about these four types of extensibility. It is our recommendation that extensibility be considered in every single design and that it should be implemented nearly every time. To not use extensibility should be an exception, not the norm. During a solution design, I like to fill out a matrix like the one below to visualize what detail needs to be included where. With this, you can start to shape the Scenario Types, cubes, dimensions, and any platform extensibility. When looking for extensibility configuration examples, look no further than our CPM Blueprint application. This application has example configurations using our leading practices. Looking at UD1 as an example, one can see our common configuration of a “MainUD1” dimension parent to summarize the BU and Cost Center details into a common dimension. This is a concept we apply to all user defined dimensions to facilitate both vertical and horizontal extensibility. To facilitate vertical extensibility, dimensional detail that is not needed in a parent cube can be collapsed by assigning MainUD1. The dimensional detail is then extended from “TotUD1” to expand into the necessary levels of detail for each data collection and reporting need. This allows both “None” and “Top” to be active at all levels in the dimensional hierarchy. Another example of extensibility on display in the CPM Blueprint application is in the cube configuration. Focusing on the financial reporting structure in this application, it follows our recommendation for a base-summary cube relationship between Business Unit and total company reporting. I commonly apply this configuration even if there is only a single child cube and a single parent cube because it opens the door to so many more options in the future: More flexibility to expand child cubes horizontally and plug in different dimensionalities Greater ability to collapse the data unit if its size becomes an issue Further future-proofing as it allows for more platform expansion with the same foundation Finally, this application also has Workflow extensibility on display. On the cube settings, you can see the connection between top level and base cubes. You can also see the Workflow suffixing applied in the CPM Blueprint application. In this example, the Actual Scenario Type has a different process flow and responsibility hierarchy from other data collections, so it has been given its own suffix of “ACT.” Budget and Forecast follow the same process flow and responsibility hierarchy so therefore share a Workflow suffix of “BUDFCST.” This allows each process to have its own configuration and entity assignment. Conclusion Extensibility in OneStream cannot be overlooked. During a solution design, each of the four types of extensibility should be weighed and discussed to see which tool is right for the job: Horizontal Extensibility Vertical Extensibility Workflow Extensibility Platform Extensibility If you conclude that extensibility is not right for you, be absolutely sure. If the choice was up to me, the benefits of future flexibility and performance reliability greatly outweigh the potential need for additional administration overhead and end user training that come with extensibility.3.4KViews9likes3CommentsThe OneStream Podcast: Expert Series - From Power User to Advanced Administrator available now
On this episode of The OneStream Podcast, longtime OneStream software instructor, Tom Linton joins Peter Fugere to talk about the roles of Power Users and Administrators. This is an in-depth and informative discussion about how to advance your knowledge, skills and career in the OneStream ecosystem that you don’t want to miss!59Views1like0CommentsThe OneStream Podcast: Foundation Series - Platform Version 9 now available!
OneStream Platform v9 introduces breakthrough platform technology, empowering Finance to go further with integrated Operational and Financial data. On this episode of The OneStream Podcast, Jessica McAlpine from the OneStream product management team joins Peter Fugere to discuss feature highlights such as Genesis and Dynamic Cube Services, and how this upgrade benefits all of your OneStream users. Listen now!75Views0likes0CommentsJuly 2025 Customer Newsletter
July 2025 Customer Newsletter We're excited to bring you the OneStream customer newsletter in a new interactive format. Quickly jump to your favorite sections, bookmark the newsletter to reference later, and share with colleagues. This month we're introducing you to the new Productivity Pack, offering discounted pricing on Splash EMEA passes, sharing how Valeo achieved 96% faster data configuration and so much more! View Newsletter The July 2025 OneStream customer newsletter includes: Product Updates - Productivity Pack & System Diagnostics OneStream Splash - EMEA Registration Now Open Quick Tips - Import templates in ESG Reporting and Planning Solution Customer Story - Valeo achieves 96% faster data configuration Readiness Toolkit - Get the most out of your OneStream data in Power BI Solution Spotlight - Planning Upcoming Events, Webinars and User Group Meetings Blog - AI Talent Shortage in Finance104Views1like0CommentsPlatform 9.0.1 Hot Fix : Database Upgrade Utility
OneStream Software has released Hot Fix v9.0.1 to address an issue observed during the v9.0.0 database upgrade process. The correction only updates the OneStream Database Configuration Utility and does not impact OneStream core functionality. This Hot Fix will ensure an uninterrupted database conversion for future upgrades to v9. Platform v9.0.1 is now on Solution Exchange, and all new v9 upgrades will be to v9.0.1. To ensure uniformity, all existing v9.0.0 customers will be upgraded to v9.0.1 during the regularly scheduled June 16 th maintenance window. v9.0.1 Release Notes are available on the OneStream documentation site. FAQ: Will the Hot Fix be Backwards Compatible with v9.0.0 Clients? Yes, the 9.0.1 Fix is backwards compatible with v9.0.0 clients. Will customers have to install the Windows desktop and Excel Add-in with the Hot Fix? No, the 9.0.0 Windows Desktop and Excel Add-In are compatible with the 9.0.1 Server and no client re-installation is necessary. Does Click-Once need to be updated as part of this Hot Fix? No, there are no changes required for Click-Once users. Users will see 9.0.1 indicated on their OneStream landing page indicating the connection to the 9.0.1 server.260Views3likes0CommentsUPGRADE REMINDER
Howdy folks! As a reminder, we are rapidly approaching the Community platform upgrade, slated for Wednesday, December 4. We anticipate downtime and some things looking wonky up until noon EST. Please bear with us as we get everything updated and sorted. Here's what you can expect while the upgrade takes place: December 4 1am- 6am EST - Community platform magic begins! 7am EST- SSO back up and running! AKA: users will be able to login again 8-12pm EST- visual enhancements are put in place For those in time zones ahead of EST, we expect you might have several hours where the community is unavailable. We apologize for that. Unfortunately, it's unavoidable BUT we promise it'll be worth it 😀 Additionally, we will post a helpful blog to get you oriented with the upgraded community. We are excited for you to try out the new OneStream Community!70Views0likes0CommentsGovernment Community Cloud v9 Upgrade
OneStream is preparing to release version v9 for our Government Community Cloud customers. This document is a guide to the v9 upgrade process. A v9 upgrade is identified as an upgrade from a pre-v9 version to a v9 version. The designated FedRAMP authorized platform release will be v9 which will be made available to GCC customers later this year. Process Overview: The v9 upgrade has infrastructure and software changes that impact applications and integrations. We will migrate from your existing infrastructure to the new v9 architecture. To prepare our customers for this process, we are providing the pre-requisites for upgrade in advance of the release. See Pre-requisites heading below. In the coming months, GCC customers will be asked to submit a Software Upgrade request in ServiceNow. When the upgrade request is submitted, it will open a Support Case to capture the outputs of the items in the Pre-requisites section below. You will be notified when this is available. Once the pre-requisites are submitted, a OneStream project manager will meet with you to plan a timeline of activities. They will be assigned to the Case, available to meet and assist throughout the process. We will provide a mirrored v9 instance for configuration and testing before your go-live. An application copy is made from your pre-v9 instance to your mirrored v9 instance. The configuration and testing period is timeboxed to 2-3 weeks. The scope of work for the test instance is configuration (for example, SIC setup or business rule compilation updates) and functional testing. We will have you compile your business rules in v9 to determine if there are any new errors resulting from the more stringent .NET 8 compiler. Experts from OneStream will be available via the Case to assist. You should also test all functionality that may not be discovered via business rule compilation. During testing, keep a log of any updates you made to the v9 test instance to remediate issues. When testing is completed, we will schedule your go-live. This is a 4–48-hour process (you will be given a more precise estimate following a database size analysis) of downtime where we copy your live databases to the v9 instances. Weekends and evenings are available. As a final step, you will re-apply the updates discovered during testing, referencing the list you generated. After go-live, your pre-v9 instances are no longer accessible; you will be live in v9. Further information: Book time with our GCC v9 upgrade team for a presentation and discussion on the v9 upgrade process by using this link. We kindly request that you submit your Software Upgrade a week before the booking time so that we can prepare by reviewing your specific pre-requisites. Pre-requisites When a v9 Software Upgrade request is submitted, it will open a Case called Cloud Migration Readiness that includes intake forms for the pre-requisite action items described below. We have attempted to put together a comprehensive list of all impacts, but given the customizable nature of OneStream, there may be additional impacts uncovered in testing. We recommend you begin work on these pre-requisite items now. If additional assistance is required before the Cloud Migration Readiness Case can be opened, please open a Case. Please note that these pre-requisites are based on expected approvals for our GCC program. The 3PAO assessment is pending. Important: We recommend customers submit their v8+ Software Upgrade in the Service Catalog to review their specific pre-requisites on the Action items tab of the Cloud Migration Readiness Case prior to reviewing this document. Pre-requisites #1 and #2 will appear as ‘Authentication’ and ‘Data Connections’ Action Items only if they apply to you. Pre-requisites #3, #5, and #6 are referenced in the ‘Customer Specifications’ Action Item. Pre-requisite #4 should be reviewed by all customers. 1. OneStream IdentityServer Customers upgrading to Platform v9 will be migrated to OneStream’s modern IdentityServer OIS authentication technology. Your identity provider continues to be supported, but a change on our side requires that your IT create or edit (depending on identity provider – see Configuration Guides below) the authentication configuration for each OneStream instance. You are impacted by this pre-requisite if you see the ‘Authentication’ item on the Action Items tab of your Cloud Migration Readiness Case. (Opened when customers submit v8+ Software Upgrade.) Pre-requisite steps: Complete any necessary technical reviews by your IT Have your IT configure the new authentication configuration for each of your OneStream instances, referencing the Configuration Guide below per your identity provider and protocol. (See Configuration Process Detail below.) Submit the values gathered in the form of the last page of the Configuration Guide to us via the ‘Authentication’ action item in your v9 Cloud Migration Readiness Case. Configuration details: Provide your IT with the Configuration guide and sitenames listed in your Authentication item. Your site name is [sitename].onestreamcloud.com, per instance. For DoD customers, your sitename is [sitename].onestream.mil. Additionally, because we are providing you with a duplicated instance for testing, configure [sitename-temp].onestreamcloud.com for each instance. This will ensure you are prepared to access both your testing instances and your final instances after go-live. Example: Your site names are ‘govcustomer’ and ‘govcustomer-test’. The sitenames to configure for v9 are ‘govcustomer’, ‘govcustomer-test’, ‘govcustomer-temp’, and ‘govcustomer-test-temp'. We recommend taking a screenshot of each redirect URL and attaching it to Authentication action item submission. This reduces the risk of error and aids troubleshooting. NIPR NET customers will also require a new CSR to be generated for the duplicate Production. This will be provided on your Cloud Migration Readiness Case. Configuration Guides: Open ID Connect OIS Entra ID OIS Okta OIS PingFed OIS SAML (with any identity provider) Reference: General documentation Identity and Access Management Guide Note: disregard the section about configuring within OneStream; for our upgrade purposes, we require it in advance of the instance creation. Use the appropriate Configuration Guide below.) For further consultation, open a Conversation on the Cloud Migration Readiness Case with the Authentication team. 2. Smart Integration Connector Smart Integration Connector (SIC) establishes secure connectivity between OneStream Cloud and data sources in your network without a VPN connection. With SIC, you can create and manage network data source integration using OneStream administration interfaces and locally manage database credentials and ancillary files. SIC transition is a requirement for v9 upgrades for several use cases. You are potentially impacted by this pre-requisite if you see the Data Connections item on the Action Items tab of your Cloud Migration Readiness Case. (Opened when customers submit v8+ Software Upgrade.) Use cases for SIC Transition: Customers who are using a Virtual Private Network (VPN) to establish data connectivity between a OneStream cloud instance and a local data source. VPN’s will not be supported with v9 or higher. Customers referencing drivers hosted by OneStream. Drivers being hosted on OneStream servers will not be supported with v9. Examples: ODBC, OLEDB (Oracle), Snowflake, Teradata, Netsuite, SAP, JD Edwards Customers who are utilizing DLL’s. DLL’s being hosted on OneStream servers will not be supported with v9. Pre-requisite steps: Complete any necessary technical reviews by your IT Create the SIC Server (or be ready to deploy it in short order) Install the SIC v9 Local Gateway on the server. You can open a Case to request it securely. Ensure you request the OneStream version that your business users are intending to upgrade to. Submit the ‘Data Connections’ action item in your v9 Cloud Migration Readiness Case. Reference: Smart Integration Connector Guide For further consultation, open a Conversation on the Cloud Migration Readiness Case with the Data Connections team. 3. Solutions & Business Rule Changes There are several substantial changes in v9 that impact business rules and Solutions. To prepare for these changes, we recommend that you upgrade to v9 compatible Solutions in advance of migration testing. The process includes multiple application copies from your pre-v9 instance (at initial data load and go-live.) If they are not upgraded in the pre-v9 instance, you will need to upgrade them each time your application is copied to v9. Upgrading in advance reduces risk and complexity. You will compile your business rules in the v9 testing instance to uncover errors, if any. We will have OneStream experts available via the Conversation feature on the Case to assist. Many customers choose to leverage a consultant for this work. Pre-requisite steps: Review Impacted Solutions List, below. Upgrade to any compatible versions in your pre-v9 instance, ahead of the v9 upgrade. Compile your business rules in your pre-v9 instance. We will ask for this on the ‘Customer Specifications’ item of the upgrade Case, when available. The purpose is to rule out any existing errors; we want to focus our efforts on v9. Prepare a list of your Solutions and their current versions. We will ask for this on the ‘Customer Specifications’ item of the upgrade Case, when available. Once the list has been provided, OneStream will return a list of Solutions that you can upgrade in your pre-v9 instance. Reference: v8 _Impacted_Solutions_List.xlsx Business Rules & Workspace Changes in v8+ For further consultation, contact the v9 upgrade team via the Activity tab of the Cloud Migration Readiness Case. 4. OneStream IP Address Changes The IP addresses of your instance will change with v9. This has potential impacts you can prepare for. We have attempted to put together a comprehensive list of all impacts, but given the customizable nature of OneStream, there may be additional impacts uncovered in testing. Pre-requisite steps: If you have non-VPN web integrations such as API or SFTP, you may need to account for new additional OneStream IP’s in the relevant system. If you can allow your domains in the relevant system instead ([sitename].onestreamcloud.com), we recommend this. Otherwise, we will provide the new Application Gateway IP once the v9 instances are built at the start of the active migration process. If your IT has a strict outbound allow list, for example Cisco Umbrella, ZScaler, or similar products, you may not be able to access the new v9 test instance until they allow it. To prepare for this, review with your IT and ensure for all your site names ([sitename].onestreamcloud.com) that sitename and sitename-temp have been allowed in relevant systems. This will help to ensure that you can access all test instances and live instances. Cloud Note: Integrations using VPN’s are not accounted for here as they will be replaced by Smart Integration Connector. Reference: For further consultation, open a Conversation on the Cloud Migration Readiness Case with the Data Connections team. 5. .NET 8 Desktop Runtime .NET is the development platform used by OneStream to build the Platform. Prior to v9, OneStream used versions of .NET referred to as .NET Framework versions. The v7.x Platform release used .NET 4.8. OneStream Platform Release v9 or later requires Microsoft .NET 8. Pre-requisite steps: Install .NET 8 Desktop Runtime for all users who will be using the Windows Client*, or prepare to install it in short order https://dotnet.microsoft.com/en-us/download/dotnet/8.0 * v9 provides a browser client for end user functionality. Users working solely with the browser client do not need the .NET Desktop Runtime installed. Reference: For further consultation, contact the v9 upgrade team via the Activity tab of the Cloud Migration Readiness Case. 6. REST API There is a potential impact to REST API, but the scope has not been determined yet. For now, determine whether you utilize the REST API as your preparedness item. We will share more information when we have it. Reference: For further consultation, contact the v9 upgrade team via the Activity tab of the Cloud Migration Readiness Case.960Views2likes0Comments