Nav hierarchy "Mass update of selected lines..." disable/restrict | Community
Skip to main content
david--garcia
david--garcia
Level 10
May 10, 2021
Solved

Nav hierarchy "Mass update of selected lines..." disable/restrict

  • May 10, 2021
  • 1 reply
  • 1241 views

Hi Team,

I have a new request to restrict/limit/dissable (Mass update of selected lines...) option which is available upon right clicking on a particular list of records, however, I need to disable it for a particular group and only on the recipient form(s)

 

 

Going through the nav hierarchy, I pulled out the following code and added it to my custom nav tree, however, it completely disabled mass of updated lines through the whole client, not just recipient, anyone has any idea on how to achieve this correctly?

 

 

<commands> <command contextual="true" enabledIf="HasNamedRight('admin')" form="xtk:massUpdate" formKeyPath="job/userArgs/recipients" formSchemaPath="job/userArgs/@nmsrecipient" label="Mass update of selected lines..." name="update" notVisibleInForm="true" rights="write"/> </commands>

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jonathon_wodnicki

Hi,

 

AFAICT it's not possible to check schema in nav hierarchy for global mass update command as it's dynamically selected and enabledif can't read its path.

Would have to put the schema check on form xtk:massUpdate and error back to the user that they aren't where they're supposed to be.

FWIW changing the UI like this isn't adding much security as users will still be able to mass update via other less convenient means.

 

Thanks,

-Jon

1 reply

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
May 10, 2021

Hi,

 

AFAICT it's not possible to check schema in nav hierarchy for global mass update command as it's dynamically selected and enabledif can't read its path.

Would have to put the schema check on form xtk:massUpdate and error back to the user that they aren't where they're supposed to be.

FWIW changing the UI like this isn't adding much security as users will still be able to mass update via other less convenient means.

 

Thanks,

-Jon

    Terms & ConditionsAccessibility statement

    Loading footer...