Announcement
ABC
Recent Activity
LIM: Understanding CSV Import Criteria 2
VERSION: PV900 SV200 PLATFORM: 9.X While importing data to the Register via CSV file, you encounter the following error message: “One or more required columns is missing data. Populate the file and reload”. This article covers tips for troubleshooting and resolving this error. When loading data via a CSV file import, you may encounter the following error message: This error message can be a red herring or false error message. It may not be because you are missing any required data, but instead it can be because the register Display Names in your file (when trimmed of spaces) do not match the Register Field Names. For example, consider the following list of Register Fields: In the example register above, all the Display Names circled in black, when trimmed of spaces, match the Register Field Name column. However, for the three highlighted, the Display Names, trimmed of spaces, do not match the Register Field Names. Why does this pose a problem? When you are importing data through a CSV file, the data load is done off a match in the first row of your file to the Register Field Name, not the Display Name. But across all LIM user screens, the Display Name is presented to the user and not the Register Field Name. So, you may assume that the load works off the Display Name that you see as a user. But that is not the case! If your Display Name is used in the first row of your file and, when trimmed, matches your Register Field Name you will be able to successfully load. But that is sheer luck! For any Display Names (trimmed) that do not match the Register Field Name, you will get the false error message "One or more required columns is missing data. Populate the file and reload”. Resolution When loading data to LIM via a CSV file, ensure that the header row in the CSV file is the Register Field Name OR align your Display Names with the Register Field Names, with or without spaces. In the example above, the Register would need to appear as below to work for all these fields: Overall Recommendation The solution you choose to employ is up to you, and your company needs. This is a design consideration when setting up your initial register. The easiest resolution, when setting up your initial register, is to use a list of Register Field Names (without spaces) that match what you wish to use as the Display Name (with spaces). This will avoid future potential problems. If your register is already set up and since you cannot change the Register Field Name, I would then choose to update the Display Name (which can be changed after the fact) to match the Field Name with spaces. DISCLAIMER: It should be noted that the focus of this technical guide is to provide general information, considerations, and guidelines for an identified topic. It is NOT to be interpreted as the ONLY approach nor a guarantee that there will not be any issues encountered by using this approach as a customer’s requirements or application configuration may render this guidance as not applicable. In addition, statements that “we believe” and similar statements reflect our beliefs and opinions on the relevant subject. These statements are based upon information available to us as of the date of this article, and while we believe such information forms a reasonable basis for such statements, such information may be limited or incomplete, and our statements should not be read to indicate that we have conducted an exhaustive inquiry into, or review of, all potentially available relevant information. OneStream does not warrant as to the accuracy of this guidance, which is provided on an as-is basis. Any forward-looking statements contained herein are based on information available at the time those statements are made and/or good faith beliefs and assumptions as of that time with respect to future events and are subject to risks and uncertainties that could cause actual performance or results to differ materially from those expressed in or suggested by the forward-looking statements. Considering these risks and uncertainties, the forward-looking events and circumstances discussed in this guide may not occur and actual results could differ materially from those anticipated or implied in the forward-looking statements.Course Announcement: Applying Dashboard Rules: Concepts and Use Cases
1 MIN READ Course Description: Using Business Rules for dashboards within workspaces, centralizes and reuses logic across the OneStream platform, enabling calculations, validations, and processes without duplicating logic. This module focuses on Business Rules, how they are used within dashboards, and how they work with workspaces, and other OneStream platform components. Delivery Types: On-Demand (OD) Duration: 2 hours, 30 minutes Availability: NAVIGATOR PASSPORT EXCLUSIVE Course Link: Applying Dashboard Rules: Concepts and Use CasesHow to Pull Workflow Certify Comment into BR Email
Hello, I'm trying to pull in the certify comment section when a user clicks on the "Set Certification Status" button. We currently are using the Workflow Event Helper to send the email when the certification is set to In-Process or Certified. Dim oEntityList As List(Of WorkflowProfileEntityInfo) = BRApi.Workflow.Metadata.GetProfileEntities(si, oWorkflowInfo.WfUnitPk.ProfileKey) emailTo = BRApi.Finance.Entity.Text(si, oEntityList(0).EntityMemberID, 8, False, False) emailBody = $"[{si.AppName}] - Status Of {sWFProfileName} WF | {sWFScenario} Scenario For {sMonth} {iYear} was changed To {If(oWorkflowInfo.IsCertified, "Certified", "InProcess")} By {si.UserName} | {oWorkflowInfo.Comment}" emailSubject = $"FM Task: {sWFProfileName} Certification Status has been changed to {If(oWorkflowInfo.IsCertified, "Certified", "InProcess")}" FBR_ConnectorLibrary.emailSend(si, emailTo, emailBody, emailSubject, emailBody) Thanks, Will
Pull in Variables from another BR
I'm trying to call a helper BR that I wrote to pull in two variables to denote our environment, but I'm getting an error message saying the extender business rule.MainClass is undefined. Background: Our GL has three environments, Dev, Prj (test) and PRD. As we promoted projects up in OneStream, I have to edit the BRs to reference the different environments. It's a pain when it comes to the SQL because the environment is part of the tableName.fieldName. Goal: to have one helper BR that has the environment variables in it and all other BRs reference this rule so I no longer need to edit them from environment to environment. The helper rule in DEV would reference the DEV tables, the helper in PRD would reference the production tables, etc. 'test code to pull in environment variables from a Helper 03-05-2026 'Define reference to business rule Dim JDE_EnvironmentHelper As New OneStream.BusinessRule.Extender.JDE_EnvironmentHelper.MainClass '<-- Update ReferencedBRName with your Business Rule 'Call function within referenced business rule If Not JDE_EnvironmentHelper Is Nothing Then Dim returnVariable As String = JDE_EnvironmentHelper.GetConnectionString(si, gateWay, envTbl) '<-- Update ReferencedBRFunctionName, param1..paramX, returnVariable type End If ' End test code 03-05-2026 The above code* is from the Connector rule that is to receive the variables, gateWay and envTbl. The error I get when I validate it is: Error at line 37: Type 'OneStream.BusinessRule.Extender.JDE_EnvironmentHelper.MainClass' is not defined. This code is directly copied from the OneStream snippets (modified for my BR name, of course) What am I doing wrong? Am I even on the right track? *line 3 above is line 37 in my BRThe 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. 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 frozen, and members will be unable to post new content, post new comments, or otherwise create anything new on the Community. The freeze will last the entire week from June 1, 2026 to June 5, 2026. 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 freeze period. Where is this happening? 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. Why are we updating the OneStream Community? As we enter a new world of AI and platforms that evolve faster each day, 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. Our goal is to empower every member of the OneStream Community with technology that enhances connection, accelerates learning, and makes engaging with the community easier and more valuable than ever. Behind the scenes, the OneStream Community team and other customer-focused teams will also gain deeper insights into how members engage with content, conversations, and learning resources. These 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. What’s next? 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!App Copy and System Parameters
Hello, When we refresh a lower environment from our production environment (app copy), the target environment's System Parameters/Secrets are refreshed from the production System Parameters/Secrets. These secrets contain connection strings to another platform and are environment specific. They must remain static. (Fortunately, I export them before a refresh and then re-import them after.) There must be a better way! Does anyone else have this issue? If so, is exporting/importing the System Parameters the only way to keep System Parameters with their correct environments? Thanks!Returning text from a BR# inside GetDataCell — possible?
I'm building a cube view column that shows combined annotations from descendants. I'm calling an Finance Cell Service BR from inside GetDataCell so I can pass dashboard params needed for the logic. GetDataCell(T#|CVTime|:BR#[BRName=..., FunctionName=CombinedComment, Flux_ID = {fluxID}]:U8#{ud8}):Name({ud8} Combined). I need to the UD8 POV member because that distinguishes what type of comment it is (CMvsPM, CQvsPQ, CMvsPYM, Ect...). The BR returns a String, but GetDataCell expects a numeric amount so the text doesn't render in the cell. Pointing the column at V#Annotation doesn't help either. Has anyone gotten BR-returned text to display in a GetDataCell with full POV/param context? Thanks, BenTech Talks: No Code Dynamic Dashboards
On this edition of Tech Talks, Sam Eburn and Jerome Marcq join Tom Linton and Matt Kerslake to demonstrate the power of no code Dynamic Dashboards on the OneStream platform. Learn how features such as Repeat Arguments and Template Parameters can be created without the need for complex code writing. To receive OnePoints for watching this Tech Talk video, please visit the link below: No Code Dynamic Dashboards
