UD or attribute to flag past restatements (Budget pot swaps)
Hello, we are about to start our work on next year budget and we already know that, following a recent restructuration, there will be a lot of pot swaps between departments (e.g. Licence costs used to sit in the department using the software but will now all sit under IT). Some of the them will be just moving a cost center and its history from one department to the next so that will be easy. Our issue is when we do a "pot swap" that moves part of a cost center. In this case we will have a disconnect when we compare actual and forecast unless we restate actual (i.e. also move the cost in actual). My question is on how best to tag/flag the "pot swap" in the actual data so that in reporting we can do like of like comparison (i.e. with past data restated) but also keep the original data. I have 2 potentials solutions: Flag the restatement using an UD: do the restatement of past periods under a specific UD so that we have the ability to see past periods with or without pot swap adjustments Use attributes: I think attributes would work but we have not used attributes in the past so not sure whether it is the best way Does anyone have the same issue and came up with an alternative solution? or has a view on the above options? Many thanks!
Preventing YTD true up for Attribute Member?
Hi, I've set up Attribute Members in my application. They are using Text fields in my UD3 dimension and the Attribute Members are in my UD6 dimension. For default Text values, it works great. However, if I want to make a time-dependent change, it does a YTD true-up on any values. For example, let's say I have a member "Member1" with the default value "Smith" and 1,000 per month. If I want the Text value to be "Jones" starting in M4, I make that change in the Text field for that period. When I view the data, the Smith row will have 1,000 for 3 months and then -3,000 in month 4 and the Jones row will have 4,000 in month 4 and 1,000 per month after that. Is there any way to prevent that YTD true up? I just want the amounts to stop for Smith and start for Jones without the true up?
Can a Data Mgmt Data Extract step be saved somewhere other than under that user's folder?
When running a Data Mgmt Data Extract step, you can chose where you want the file saved: However, the name you provide always starts under the File Share\Applications\[App Name]\DataManagement\Export\[User Name] folder. So, the above extract would show up as File Share\Applications\MyApp\DataManagement\Export\Phil\20211202\CubeData.csv We need these extracts to be available to users who do not have access to the individual user folders on the File Share (i.e. - they aren't Admins) Is there a way to have the Data Extract saved to a truly user defined location, like Application Database\Documents\Public\DataExtracts? How could this be done? If you run the extract from a business rule are there arguments you can pass into the data management call to override the export path? Or is there a way to programmatically move the file after it's been created? Thanks,
usage of Aggregated member from Consolidation dimension
At the moment the Aggregated member uses the IsConsolidated property to aggregate or not. Do I have any option if I wanted to aggregate a member but not consolidate it? With the introduction of the new member Aggregated, is there going to be a IsAggregated property created or will it always work with the IsConsolidated property? ThanksUsing Variance Explanations and UD8 (Dynamic calc periods) together
Originally posted by Felipe Alcorta Hello: We'd like to incorporate variance explanations into our cube views. If the cube view shows one periodic comparison (e.g. Jun YTD CY vs June YTD PY), we have a corresponding dynamic calc that calculates the variance and we can use the (out of the box) variance explanation from the View dimension in order to have comment/explanation functionality. However, if we have multiple comparison period in the same column template/cube view, we are unable to. If we take the same approach as one periodic comparison, the same comment would appear in both comparison columns since there's nothing to distinguish which periodic comparisons are being explained against. We tried using a placeholder UD8 elements (no formulas) in addition to the variance explanation from View dimension but OneStream says it's an invalid cell. Advice?
Automatic update of Metadata in OneStream?
Does it make sense to get OneStream Metadata (eg Entity, Cost Center etc) be updated automatically from upstream source system such as SAP? I would have thought it would be far too risky but just want to check if anyone out there had ever come across such requirement and what approach you deploy so that metadata between source ERP and OneStream are in sync? Thanks in advance for sharing your experience.
