Fiscal Year Change
Hello, I am wondering if there is any way to change a fiscal year once we have been using the application for quite sometime (several years.) Our current Fiscal year is 2025 so all the data is being imported into year 2025, but we now need to adjust our fiscal year one year back. So everything in 2025 becomes 2024. Is this possible? Or what options might I think about? Would I need to setup and start using a new scenario? Any ideas, comments, suggestions would be greatly appreciated. Thank you136Views0likes5CommentsMember Filter on Scenario properties
I would like to apply a member filter on a scenario, which will return a list of a scenarios based on it's properties like Name, Description, WorkflowTime, WorkflowStartTime, and WorkflowEndTime...i.e. WorkflowTime = |someYear| or WorkflowStartTime = |someYear| or WorkflowEndTime = |someYear| I can do this S#Scenario.where(Name contains paramScenario) I can do this S#Scenario.where(Description contains paramDescription) I cannot do this S#Scenario.where(WorkflowTime = 2025) I cannot do this S#Scenario.where(WorkflowStartTime = 2025) I cannot do this S#Scenario.where(WorkflowEndTime = 2025) What am I missing?Solved28Views0likes4CommentsChanging Start Year of Application after going live
Hello, Working with a client and implementing a marketplace solution that potentially requires us to go to a year that is before the start year of the application. Is there any harm in changing the start year to an earlier year? Those years will not be used for their normal operations nor feed data to the cube, so not sure if there would be an issue changing this. Any thoughts? Thanks, AJSolved22Views0likes1CommentCube View DatePicker, Time Zone and Custom Calculate
We're working on a solution, where users can enter and view a date through a Cube View using the Cell Type Date. The challenge is how OneStream handles date's (datetime) with time-zones. When a date is saved to the backend, it's converted to UTC time-zone. The Date component in the Cube View is also Time-Zone aware, so that it uses the local time of the user, to convert back from the backend UTC to local-time. The challenge with this is 2 fold: 1) Assuming we would calculate a rent for a given period. The user, based in CET time-zone, enters 2022-1-15 using the Gridview. This date is converted to 2022-1-14 as UTC (2022-1-14 23:00:00). Using a Custom Calculate method to calculate the rent from start (2022-1-15), now adds one day more, as the server time is UTC. (don't mention Daylight Saving Zone) 2) If another user, based in US Central, is reviewing data in the same Grid View (and same POV), this user will see a wrong date, as the server UTC date, is converted to this user's local time Is there a way to specify in the Cube View, that when using the Date/DateTime picker, that the component should ignore time-zones? Or are there other usable solutions for this issue? Cheers5.4KViews1like11CommentsChange of reporting period for entity (From Jan- Dec to Apr-Mar) in OS
Hello All, Is there a functionality ofChange of reporting period for entity (From Jan- Dec to Apr-Mar) in OS. For Example, if currently I am working for FY Jan to Dec but in future, I want my FY to be changed to April - Mar, so how can I achieve the changes without getting any impact in the historical data?464Views0likes6Comments-Ve Actuals in Oct TImeperiod
I have stats account, user is input the numbers for September Time period at base level in Actual scenario for Periodic combination and the -ve number are showing in October TImeperiod. that -ve number is YTD of September. as user is requesting to clear that October Actuals -ve data. Is there way that we can delete and also, I am surprised how this -ve number flow into the Oct Time Period. The flow is EndBal_Input. users are entering the number from quickview. Any suggestions to solve this issue?166Views0likes1CommentSwitch data access security on users by time
I'm sure this question has been asked before in the forum, but I just couldn't find it in the community. We have this requirement where in the same Actual scenario, Corporate (a group of users) can only access the Actual data after the actual data is finalized by different entities. Any point of time leading to Day X, the entity has the control to pull the switch on releasing the data access to Corporate. On Day X, all the data is made accessible to Corporate. I thought about slice security, but it doesn't seem to accommodate this requirement due to the static nature of the DU filter; neither does Conditional Input, which doesn't control the general data access. Can someone please shed some light here on this design whether it's possible to lock down a group of users by time period?353Views0likes4Comments24 Month PLP Dataset - Import to cube
Hello All, We have setup People Planning for 24 periods. We need to import the data into a cube across 2 years/24 months. Wondering the best approach. We have flagged Allow Loads After Workflow View Year as "True". We have tried using "Range" in the Workflow Tracking Frequency. This approach works, but the fact that we can't change time periods in the Scenario, creates some monthly and annual process management issues. Anybody use an alternative approach? Thanks, Scott3KViews0likes9Comments