Skip to main content
Nintex Community Menu Bar

I have a Nintex form where there is a panel that should be locked down in edit mode unless the person editing the form is a member of one of five groups. I read that this fn-IsMemberOfGroup function is limited to only two groups.

This caused an error in the form - where some of the other approvers received an “this item had not been shared with you error”...

fn-Or(fn-Or(fn-Or(fn-Or(fn-IsMemberOfGroup(“Group1”),fn-IsMemberOf(“Group2”)),fn-IsMemberOfGroup(“Group3”), fn-IsMemberOfGroup(“Group 4”),fn-IsMemberOfGroup(“Group 5”))))) && Is Edit Mode

Basically, we don’t want the Created By/Requestor and their “manager” (a people picker field) to edit that panel...if the fn-IsMemberOfGroup is limited to only two groups - is there a different rule I can use to prevent the requestor in updating that panel?

 

Hi ​@isabellamai,

I think the issue in that function is actually in the Or functions.  I didn’t have an issue combining more than 2 sets of IsMemberOfGroup functions.  I configured my rule like this:

(fn-IsMemberOfGroup("Home Owners") || fn-IsMemberOfGroup("Home Members") || fn-IsMemberOfGroup("Home Visitors")) && Is Edit Mode


Hi ​@isabellamai 
Has your question been solved?


@brent_read ​@MillaZ - thanks for the info/checking in. Still having a problem with the access - using the above and am not sure if it’s also associated with the fact that the workflow originally stops inheriting permissions, and then create unique permissions based on a location field (choices: New England Approvers, Midwest Approvers, etc.); and there is one panel where access is restricted to the location Approvers, and higher leadership for editing; however, the requestor and his manager (Manager POC) should still be able to view it --- just not edit.

  • If New England Approvers were selected...(fn-IsMemberOfGroup("Finance") || fn-IsMemberOfGroup("New England Approvers") || fn-IsMemberOfGroup("HR")) && Is Edit Mode
  • If Midwest Approvers were selected...(fn-IsMemberOfGroup("Finance") || fn-IsMemberOfGroup("New England Approvers") || fn-IsMemberOfGroup("HR")) && Is Edit Mode

The groups came back and said they still saw a “Sorry this site has not been shared with you” error. I tried different variations:

((fn-IsMemberOfGroup("Finance") || fn-IsMemberOfGroup("New England Approvers") || fn-IsMemberOfGroup("HR")) && Is Edit Mode

((fn-IsMemberOfGroup("Finance") || fn-IsMemberOfGroup("New England Approvers") || fn-IsMemberOfGroup("HR")) && Is Edit Mode)

((fn-IsMemberOfGroup("Finance") || fn-IsMemberOfGroup("New England Approvers") || fn-IsMemberOfGroup("HR") && Is Edit Mode)

 

Can you verify if the original syntax was correct?


Hi ​@isabellamai 

The error you’re describing is a Sharepoint Permissions error and shouldn’t be something controlled by the form itself.  It sounds like you need to assign the people getting the error a read only permission to the item itself rather than doing anything to the form.


@brent_read  - I believe my permission is set correctly. The approvers have full control, while the Requestor (created by) and the direct manager (people picker) have contribute permissions. Once the requestor submits the form, they are not allowed to edit this one panel that has the budget data -- and that’s where the above rule is used - validation rule to only allow Finance, Approvers (New England/Midwest/etc.), and HR edit access. The approvers are the ones receiving the errors. When I used the fn-Or(fn-IsMemberOfGroup(“Group1”),fn-IsMemberOf(“Group2”) && Edit Mode for 2 groups - it worked fine - but once I added a third group - the errors started.

 


Hi ​@isabellamai 

Can you send a screenshot of the error you’re seeing?  Nintex forms doesn’t alter or control SharePoint permissions, so the “Sorry this site has not been shared with you” error you’re seeing is coming from something on the SharePoint Side.

I’d also recommend navigating to the item permissions page on one of the items where a user is seeing the problem and using the check permissions button in ribbon to verify to permissions of the user.

If that shows that the user has permissions to the item itself then I’d have the user open their dev tools and check the network tab to see what request is throwing the unauthorized error to the user when they load the item.


Reply