View Member Issue on Cash Flow Report
Hi All, I am working on a Cash Flow Cube View to show the beginning cash, ending cash, and change in cash (activity) in three separate rows. All the base cash accounts are under the new parents (beginning cash, ending cash, and change in cash) in an alternate account hierarchy for the Cash Flow. We are using the BegBal_Dynamic flow member from the Blueprint app for beginning cash, EndBal for ending cash, and Activity_Calc for the change in cash. Figures are flowing in, but for these accounts the columns have a view member set to Periodic, QTD, and YTD. The problem is that figures are not representative of the View member, that is to say that they are all the same on the ending cash. Below is a screenshot and the Cell POV for each of the members. I am happy provide any other screenshots or additional information to get a resolution on this. Thanks in advance! MTD (Periodic): Cb#Batesville_Cons:E#LE_TOT:P#?:C#Local:S#Actual:T#2025M5:V#Periodic:A#End_Period:F#EndBal:O#Top:I#Top:U1#CC_TOT:U2#Product_Total_Core:U3#Reported_GAAP_Tot:U4#PayType_Total:U5#Initiative_Total:U6#None:U7#None:U8#None QTD: Cb#Batesville_Cons:E#LE_TOT:P#?:C#Local:S#Actual:T#2025M5:V#QTD:A#End_Period:F#EndBal:O#Top:I#Top:U1#CC_TOT:U2#Product_Total_Core:U3#Reported_GAAP_Tot:U4#PayType_Total:U5#Initiative_Total:U6#None:U7#None:U8#None YTD: Cb#Batesville_Cons:E#LE_TOT:P#?:C#Local:S#Actual:T#2025M5:V#YTD:A#End_Period:F#EndBal:O#Top:I#Top:U1#CC_TOT:U2#Product_Total_Core:U3#Reported_GAAP_Tot:U4#PayType_Total:U5#Initiative_Total:U6#None:U7#None:U8#None
Spreadsheet tool in v8.5 - does it work?
Trying to confirm if the spreadsheet tool in v8.5 is working for anyone in the following manner... Created dashboard with the spreadsheet tool. The page renders fine... However, when doing something as simple as Save As, the following message is generated. Excel file is defined in the configuration. One client mentioned this, so I tested this on another client with the same results. Heard this is fixed in v9.0. Is this correct or am I missing something? Thanks for any input! Ed Puente
Data Cells become invalid when Flow Processing Type is enabled
When the Flow Processing Type "Is Alternate Input Currency for All Accounts" is enabled on a Flow member (as shown below Data Intersections become invalid for that Flow member and Foreign Currencies (USD, CAD).Entity BU_200 default currency is EUR. Note that when this property is not enabled the foreign currency cells are valid. My understanding is when this setting is enabled the foreign currency data cells should be enabled for data load or input. Appreciate any clarification on this.
Smarter Data Loading: How OneStream Transformation Rules Automatically Handle New Members
In the world of Enterprise Performance Management (EPM), clean and accurate dimensional mapping is essential for a reliable reporting process. Fortunately, OneStream makes this easier through its robust Transformation Rule framework, which intelligently handles new dimension members automatically. Whether it's a new GL account, cost center, or entity, OneStream’s transformation engine ensures that new data doesn’t derail your process, even before user intervention. 🔍 Key Benefits Dynamic Member Detection When a new source member enters the system—say, a newly created account in the ERP—OneStream flags it immediately as “Not Mapped” in the staging area. This provides the user or administrator with a clear indication that attention is required. Mapping can then be quickly added or adjusted to keep data flowing seamlessly. Centralized and Flexible Maintenance Transformation rules support Wildcard and Dynamic Mapping, making it easy to set default routes for unknown members (e.g., directing all new accounts to a placeholder for Unmapped Accounts). From there, consultants or admins can reassign the correct mappings when ready. This approach provides control without interrupting the load process. Built-In Mapping Validation There’s no need to build dashboards or manual reports to detect mapping issues. OneStream’s Data Source and Transformation Rule editors include built-in validation tools to identify unmapped or incorrectly mapped items before they affect results. This enables early detection, faster resolution, and reduces dependence on visual checks. ✅ Why This Matters By leveraging these out-of-the-box capabilities, organizations save time, reduce risk, and streamline their integration workflows. Consultants can focus on higher-value tasks instead of constantly updating mappings, and end users can trust that data loads will highlight issues automatically, before reporting is impacted. Please keep it simple. Do you agree that OneStream handles what it's built to do?Account Attribute: In Use versus Allow Input
Hi all, We have hundreds of historical (no longer valid) accounts sitting in a cube and we are looking at ways of de-cluttering resulting data retrievals to avoid seeing them. But additionally, we want to prevent any accidental loading to these accounts from the source system. For reporting, I know we can populate one of the text fields with some text and then combine that with a Where() clause to filter out these old accounts. But, from a data load perspective, just wondering what the risks / benefits are of utilizing either (or both) of the In Use or Allow Input attributes; to prevent accidental loading of data there. We want to be able to continue to see any historical data for these accounts and be able to drilldown from the parent account and see that data. There are no member formulas associated with these - they are all base accounts. We don't care about the Scenario/Time specificity capability If anyone is using these attributes would very much appreciate any recommendations or hearing what your experience has been (before we go through the effort of testing either of these options). Many thanks, K.
Issue Retrieving Text Property from DynamicCalc Accounts in UD8
Hi all, I have a DynamicCalc account where the Text6 property is populated. I also created a UD8 member that dynamically retrieves the POV account and returns its Text6 property. In my Cube View, I set the POV for this UD8 column to Annotation. This works well for all non-DynamicCalc accounts... I can successfully retrieve and display the Text6 property in the Cube View. However, for DynamicCalc accounts, the Text6 property doesn't appear. It seems like OneStream can't resolve the property for DynamicCalc members in this context. Has anyone encountered this behavior? Thanks in advance! UD8 member filter:Mass modification of a Metadata member attribute
Hi all, Does anyone happen to have the correct syntax for an XML file that modifies a single attribute (member property) and can be uploaded to OneStream without resetting other member properties? A bit of background, I have to add content to the Text7 field of over 3000 members. I tried one version of a XML that only referred to the Text7 property for a single member But when I loaded the xml, some (but not all) of the properties for that member reverted back to original defaults. On the plus side, it DID update the Text 7 field. I'm clearly not defining my XML properly so if anyone has an example of the syntax I can use to update a property without affecting anything else, I would love to see it. I realize I can extract all 3000 members to an XML, but if the Text7 property is not assigned anything, then that property doesn't get included in the extract (otherwise I could simply do a global search/replace): in order to fix this I would have to write a script to run against the contents of the XML and 'add' a line identifying that property and it's contents. I'm hoping there's something more straightforward out there? Fingers crossed. Thanks in advance for any examples you might have.
Dynamic Member addition in version 9
We are looking for some help in direction to build dynamic member addition to a dimension using extensible business rule in version 9.0 We have tried to use the code that is used in earlier versions which uses declaration like "Dim newMember As New Member" but it does not work anymore in version 9 as it gives error when assigning values to newMember.Name property and some search suggests that we now need to use "Dim newMember As New MemberEx" Using this declaration results in error compiling the business rule. We are looking for some help/direction on this.Hybrid Scenario – Pre-Aggregated Member Setup for Entity Summarization (V8.4)
Hi Team, I’m working on a Hybrid Scenario setup where the goal is to copy data from a source scenario to a management (MGT) scenario. This allows the MGT team to work with the data independently, using their own workflow with high-level access. So far, the base data copy works well. However, I want to summarize entity data in the target scenario so that users only see Entity parent nodes, while maintaining visibility of all other 17 dimension members (Account, UD1-UD8, etc.). To achieve this, I tried creating a dummy parent member (Entity X) in a new Entity dimension that mimics the top-level parent from the legal entity hierarchy (Entity Y). My intention was to use this structure in the Pre-Aggregated Members field in the Hybrid Scenario configuration, effectively copying: Entity X = Entity Y Unfortunately, this method worked successfully in Version 7.4, but does not appear to function as expected in Version 8.4. Maybe in version 9.0 +, we can successfully configure pre-aggregated entity mappings for Hybrid Scenarios? Can we customize this to version 8.0 and above? Would appreciate any advice or examples from the community if you’ve made this work in your applications. Thanks in advance! Chris
