We have some group of base customers under different parents with text property, and we are planning to block input to those customers in all the input forms if we use dimension property Allow input 'false' then it will block input but after that update during close FPA team should do adjustments for those Customers. Can we do it with irrespective of that dimension property false update. Is there any option that without updating input forms (CUBE VIEWS) with customer (UD2) parameter or with the help of business rule can we override that dimension property Allow input 'True' by running DM Step for certain customers when we give them in DM JOB and revert again to false after inputs through DM step. Please suggest your solutions.
The "In Use" setting on the dimensions turns the intersection pink so that it appears as an invalid intersection, for all users (even native administrators):
And the "Allow Input" setting on the dims turns the intersection green so it appears read only, again for all users including native administrators:
There are many ways to handle this requirement:
Create a form where those customer UDs are not shown thus now allowing input (.Where(Text# = 'whatever') and only grant access to that WF profile and form to the users whom you do not want inputting
Create another form where the FP&A folks can get to it and those intersections are shown
Create a WF Channel on U2 and use the WF channel combined with the WF profiles and forms to control which WF profiles people can get into to enter data
If the Customer U2 is a parameter in the form, create a security group that you attach to the "Display Member Group" on those UDs and allow some people display access and others not. The "Display Member Group" security property is a good way to "hide" members from pick lists and parameters
Use a NoInputBR on the cube where if users are in a specific security group (or certain WF profile), you grant them access and if not you turn those intersections to read only
Use Slice security on the cube(s) to grant all access or only read access to those intersections
You may be able to get the DM job and BR to flip the In Use or Allow Input from True to False, but this seems more complicated and less elegant than perhaps one of the above options.
Others may have ideas too, these are just some that came to mind for me. If this is just a requirement around forms data entry and the U2 is a pick list parameter on the forms, I would probably lean towards using the "DisplayMemberGroup" on those customers and create a security group that some people can see (FP&A) and others cannot see (people who should not input). That will remove those U3 customers as a choice in the parameter on the form.
