Creating a Record Level Security (RLS) rule or Field Level Security (FLS) rule that employs a user name or group name value in the formula can result in a broken rule if the name contains a comma.

Symptom

If a user whose user name or parent group name contains a comma is unable to see certain records (or fields) that are expected to be viewable when logged into OpenPages, it could be because the record or field level security rule's formula does not contain the intended user or group name.

For example, a rule is being created for the "SOXBusEntity" object type that employs the "Executive Owner" object field. In this example the user's profile has the Display Type attribute of the "Executive Owner" field defined to be a Group Selector. The user selects the group name of "Workflow, Reporting and Others" from the list of available groups for the value of the 'Executive Owner' field.

The presence of the comma in the group name results in two separate values being specified in the IN GROUP clause: 'Workflow' and ' Reporting and Others', separated by a comma as shown below:

     [SOXBusEntity].[OPSS-BusEnt].[Executive Owner] IN GROUP ('Workflow', ' Reporting and Others')

whereas the formula that was actually intended for this rule is supposed to specify just the selected group name in the IN GROUP clause:

    [SOXBusEntity].[OPSS-BusEnt].[Executive Owner] IN GROUP ('Workflow, Reporting and Others')