O#Forms submissions to locked forecast scenarios
Hi all, How do you handle preventing users from accidentally loading data via an excel XFSetCell or QV submission to O#Forms/O#BeforeAdj on a scenario that’s locked on the workflow in OS? I’ve submitted this via OS support and there’s an enhancement request for “Requesting option to prevent users from submitting data in Excel via XFsetcell or QuickView” but there’s no workaround that they can provide. Our FP&A users load all data via excel and they’re generally educated enough to know what dimensions to change, but sometimes the communication doesn’t go out timely enough from corporate FP&A to stop loading adjustments (though the scenario is locked promptly on the workflow) and so we run into this issue. Any thoughts or feedback would be welcomed! Thanks!
How to provide access to a dimension to a user
Hi Team, Hope you are doing well and I would like to know the process to provide access to a particular dimension as user is facing an issue Steps I performed: 1.Created a group under System 2.Created a user with OKTA verification 3.Updated the group to the dimension in Access Group property. 4.Assigned the user to that Group But user is getting as below Error:Application access denied because user account is not found or has been misconfigured. Contact your system administrator. ThanksInvalid Intersections on all lines of a data load
Hello, I am trying to limit the access of certain entities so they they can only see there own entites, i have it set up on the entities, cube, and the workflow profile so they have their own groups for each of their own set of data. The only issue is when they load their text files it is fine but when they run the transformation rules every line shows up as an invalid intersection and the error message is "No Security Access" for each line. I saw an article that recommended going to data access on the cube but i tested them empty and i tested them with what i thought the escalation rules should look like with no luck. So i wanted to see if anyone had any other ideas on possible solutions or where i might be wrong. Thank youParent entity write security & Annotation-type view members
Hi all, Who utilizes Annotation or the other similar view members for writing text into OS? If so, do you give write access to parent entities? We’re looking to use VarianceExplanation to capture threshold explanations but we review and explain this data at a parent level and currently our entity parents all have a write access group of Nobody. I’m looking to narrow down when write access would be given at a parent entity level so I can judge what we’re opening ourselves up to if we decide to change security. Any insights are appreciated! Thanks, Nicole