NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm

Field Security Behaving Differently In NEXT

Owned by Cameron Betsch (Unlicensed)
Last updated: Jan 29, 2019 by Diane Hogan (Deactivated)
1 min read

Application Scope: CORE

Problem

Security behaves differently in NEXT than it does in Classic in that in Classic users have access to the fields in a specific fieldset, but in NEXT they do not.

Cause

In Classic, a secured fieldset only needed View rights to edit the fields inside it.  In NEXT, the user needs to be in a role with View and Edit rights.

Solution

Add Edit rights to the Role that includes the fieldset Entity in question.

  1. Go to System Admin  > Security > Roles.
    The Security Roles list is displayed.
  2. Search for Roles with the security entity in question. This should be in the format gen_DataformName_FieldsetName.



  3. Ensure that you update the role selections to include View and Edit as in the image above
  4. Save your settings


Article Images:


NOTICE: You are in the old ClientSpace Help system. Please link to the new ClientSpace Help here https://extranet.clientspace.net/helpdoc/home/ClientSpace.htm