Announcement
ABC
Recent Activity
Task Manager Dashboard Configuration
I have to create a task manager build that does not include weekends in the duration. We have tried adding the weekends to holiday profiles and excluding them from the explicit day map, but the duration will always include the weekends. Right now, I have due dates on weekends an holidays even when calling them out in the Holiday Profile and setting each one with an offset of 1. Is there a work around for this or any other solution to have the durations skip weekends/ due dates not be due on weekends or holidays?
New Episode of The OneStream Podcast Now Available!
1 MIN READ 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!Business Rule | One-to-One Transformation - E# Parent to its first E# Base
We need your help to Import flat files: 1. Number of Rows: > 100k 2. Organized under E# Parent Members: a few thousands 3. E# is extended We've been fortunate to be advised to build a BR to generate a one-to-one Transformation Rule file. - E# Parent to its first E# Base Is it possible for you SMEs to be generous enough to share with us/Community: - a sample BR to look up its first E# Base Member of an E# Parent Member - under extended E# - how to call that BR in an Import Workflow Thank you, OS SMEs.
Public Overloads Function GetBusinessRules
I have seen several MaketPlace solutions rules that give me a warning message when I compile in v 7.1.1. See the example below: Warning at line 410: 'Public Overloads Function GetBusinessRules(si As SessionInfo, brType As BusinessRuleType) As List(Of BusinessRuleSummaryInfo)' is obsolete: 'This is a temporary function used by Marketplace Solutions for backwards compatibility with old XF versions. Please change your code to use supported functionality.'. Not sure how these rules will behave when we upgrade to v 8.5, but I was wondering if there is an easy fix out there which will remove this warning message.Course Announcement: OneStream Architecture: Design Decisions
2 MIN READ OneStream Global Education Services is excited to announce the new OneStream Architecture: Design Decisions course available now as an Instructor-Led Training. Course Description This instructor led course is tailored for consultants who are looking to expand their design decision-making skills or are pursuing to become architects in the future and are working with OneStream applications. It tackles common design challenges and equips participants with skills for informed design decisions that enhance performance, flexibility, and user-friendliness. Students will engage in instructor-led sessions, practical use cases, role-play, and collaborative activities to gain hands-on experience in developing and justifying design proposals. The course focuses on requirements gathering, guiding design principles, and key areas for effective application design (such as Extensibility and Data Units). Participants will also learn to communicate the trade-offs and benefits of design choices to customers, ensuring they can advocate for optimal solutions effectively. Delivery Types Instructor-Led Training Availability Customers Partners Employee Who Should Take This Course? The OneStream Architecture: Design Decisions course is designed for consultants with considerable OneStream knowledge who aim to enhance their design decision making skills, balance performance and user-friendliness, and effectively advocate for optimal solutions. The ideal student for this course: Has experience and working knowledge of concepts such as Extensibility, Cubes, and Data Integration as it will be needed to ask customers the right questions. Are proactive problem-solvers who seek to understand the trade-offs and benefits of different design choices to optimize OneStream implementations. Are eager to engage in interactive learning environments, leveraging group discussions and roleplay to refine their design skills. Duration Instructor-Led Training (ILT): 1 day Prerequisites Prior to taking this course, you should have: Completed the First Project Readiness Learning Path or possess equivalent knowledge. Completed the OneStream Architecture: Designing an Application course or possess equivalent knowledge. At least 2-3 years of software implementation experience in the financial software industry, including 2-3 years of experience with the OneStream software. Micro Credential Upon completion of this course a micro credential will be issued. Course Schedule Date Modality Time zone September 12, 2025 Virtual Eastern September 25, 2025 Virtual BST October 2, 2025 Virtual Eastern October 9, 2025 Virtual BST November 4, 2025 Virtual Eastern November 10, 2025 Virtual GMT December 2, 2025 Virtual Eastern December 8, 2025 Virtual GMT Dates and times are subject to change. Please visit OneStream Navigator for the latest schedule. Important Links Register via OneStream Navigator: OneStream Architecture: Design Decisions Course Description PDF Pricing and Learning Paths PDF
OneStream 9.0 file explorer error
Hello, I installed OS 9.0 on premise version recently and I am having the following error when I try to upload a file: You can find below the error details: Unable to load file.An error has occurred. BadRequest. User Interface Stack Trace: at OneStream.Client.Api.FileExplorerServiceReference.FileExplorerServiceClient.UploadFileFromStream(XFFileTransferRequest request) at OneStream.Client.Api.FileExplorerServiceReference.FileExplorerServiceClient.<>c__DisplayClass370_0.<BeginUploadFileFromStream>b__0() at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) Do you know what is the cause of this issue? Thank you in advance. Antony
Extensibility 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.All Aboard the CPM Express!
1 MIN READ The replay of Tech Talks: All Aboard the CPM Express is now available! The link below will expire on August 15th so don't wait. https://thoughtindustries-1.wistia.com/a/xbcxtlrhnttudi5 You can also watch this replay, and all episodes of Tech Talks, on OneStream Navigator as part of your Passport subscription.Coming Soon: IdeaStream Revamp
2 MIN READ Greetings OneStream Community! As we continue to make updates across our Community, we decided it was time to take a look and freshen up IdeaStream. While we have already planned some changes which we'll outline below, we'd also like to gather your thoughts, opinions, and impressions of IdeaStream currently. Please take this IdeaStream Survey to help us shape the future of IdeaStream. In the meantime, we do have some exciting upcoming changes to the IdeaStream site management. Please read on to see what we'll be working on over the next couple months! Improved Moderation First, we are exploring ways to enhance your experience and our engagement with your ideas in IdeaStream. In the revamp, we will have dedicated moderators reviewing the ideas and facilitating product review as ideas gain momentum. This means each idea will see dedicated moderation to help enhance your submission process, which will include an initial review to ensure completeness (a request for more information if required) and relevant tagging on new ideas. All ideas will be moderated within 3 business days of posting and will either result in your Idea being updated from “New” to “Gathering Interest” OR a moderator will request additional information on your Idea using the “Needs Info” status. This is meant to give ideas the best chance possible for engagement in the Community and clarity for our Product Owners reviewing all your great submissions. Finally, we are updating the available tags and categories to better serve the ideas that are being created, and we will continue to update tags on a more frequent cadence in the future. IdeaStream Reporting The reporting on the page is also a focus for continuous improvement. We are reimagining our ranking lists to give you real-time insight into what’s new and what’s trending on the Community Ideas page. If you have suggestions for reporting formats or topics, please let us know and we will continue to add to the page! Audit & Archiving We are working to make the number of ideas more manageable for you. We know there is a lot to sift through currently so we’re doing a little housekeeping on the site. Over the next few weeks, aged ideas with low engagement will be closed under the following criteria: Ideas posted before 2025 with fewer than 5 votes - OR - There is a duplicate idea created in IdeaStream We'll continue to update IdeaStream articles including Frequently Asked Questions, the About IdeaStream article, and tips for a successful post in the Submission Guidelines as we implement these changes. Thank you for your ongoing engagement with OneStream, and all the great Ideas posted so far! Provide Your Feedback We’d like to hear your ideas on how to make the process clearer, the interaction more effective, and most importantly to give you meaningful engagement with our Community and product teams. If you are interested in sharing your thoughts, opinions, and impressions of IdeaStream, please take the IdeaStream Survey You may also reach out to ProductGrowth@onestreamsoftware.com with “IdeaStream Thoughts” in the subject line.
