Skip to main content

Hi,

I have a dimension formatted property in a transaction list. I want to restrict the items in the dropdowns based on users. Applying data access rules achieves this only partially it seems. While the users cannot see the items that are not assigned to them once they make the selection from the dropdown (the input simply disappears), while making the selection they are able to see all available items in the list. How can I restrict this?

Hi ​@tjain02 ,

Can you try to apply the access rights rule to that “dimension” list,
and then the users shall be able to view only those items in the dropdown to which they have access to.


@Chahat , I have already tried this but it does not seem to work. I can still see all items in the dropdown. I am trying to apply this rule on the community dimension. This dimension is being used in the capex input list as a property. Can you confirm if I have applied the right rule?
 

 


Can you try to use the following?
Apply Read & Write accesses to ‘Specific List Properties’ .

Also, have you tried using the Impersonate feature if you’re able to view all the options or only the applicable options/items in the dropdown?


Hi ​@tjain02 ,

Since you need to show the selective dropdown, hence, you’d need to apply the access rights to the dimension list directly.
Please use this:
Choose List : Community
and select all the properties of the community list in this rule.


This approach should work for you, let me know if you need any help.​​​​​


By following the above rule configuration i.e. “Specific List Properties”, and then choose list “Community” and apply configuration to all properties of the “Community” list


Hello ​@tjain02 ,

Thank you for your question!

There is no built-in way to restrict the dropdown options in transaction lists based on user access rights at the selection stage. This is a known limitation.
But you ca use the workaround provided by ​@Chahat (Thanks for you help!). You can restrict dropdown options dynamically through dependent dropdowns, but these are based on relationships between properties, not user access.
I invite you to submit an idea in the Ideas section of the Pigment Community for future product consideration.
I remain available if you have any questions.

Best regards,


Reply