Use a field security policy to define for which forms, tables, or fields editing is locked or allowed.

If the form mapping is recorded and applied to a field security policy, edit the table setup.

In the table setup, you define the tables, and optionally, forms, to which the field security policy applies. You also define how the policy is applied to the tables and forms.

The security level defines how to set up the policy and how it is applied:

Security level Description Field setup Condition setup
Table

Editing is locked or allowed for the whole table.

Only define one field setup record if you want to apply conditions. For this field setup record, these fields must be empty: Field name, Control name, and Dimension name.

The settings of the Default action field and Skip field are not considered.

You can only apply generic conditions, for example, on user or role.
Table field

Editing is locked or allowed for specific table fields.

Define the desired field setup records.

The settings of the Default action field and Skip field are considered.

Note:

The field setup default action overrules the table setup default action. For example, to allow editing of a few fields of a table with many fields, set the default action of the:

  • Table setup to Lock edit.
  • Field setup to Allow edit.
For each field setup record, you can define the desired conditions. You can only apply generic conditions, for example, on user or role.
Record Editing is locked or allowed for the whole record.

Define one field setup record. For this field setup record, these fields must be empty: Field name, Control name, and Dimension name.

The settings of the Default action and Skip fields are not considered.

Apply conditions to define the records to which the policy applies. Define the conditions based on record data.

For example, editing a record is only allowed if the:

  • Record has a specific status.
  • Customer belongs to a specific customer group.
  • Item is within a range of item numbers.
Record field Editing is locked or allowed for specific record fields.

Define the desired field setup records.

The settings of the Default action field and Skip field are considered.

Note:

The field setup default action overrules the table setup default action. For example, to lock editing of a few record fields, set the default action of the:

  • Table setup to Allow edit.
  • Field setup to Lock edit.

Apply conditions to define the records to which the policy applies. Define the conditions based on record data.

For example, editing a record field is only allowed if the:

  • Record has a specific status.
  • Customer belongs to a specific customer group.
  • Item is within a range of item numbers.

 


Standard procedure

1. Go to Dynamic field security management (Preview) > Policies > All field security policies.
2. In the list, click the link of the desired field security policy.
3. Click Edit.
4. Expand the Table setup section.
5. In the list, find and select the desired record.
6. If you applied the form mapping including form-specific setup, the form name is entered in the Form name field. If you want to make the setup table-specific instead of form-specific, remove the form name from the Form name field.
With a form name:
- Filled, the policy is applied to the defined form only.
- Not filled, the policy is applied to all forms that use the defined table.
  In the Form name field, enter or select a value.
7. In the Description field, type a value.
8. Choose one of the security levels.
For more information, refer to the table in the description of this topic.
  In the Security level field, select an option.
9. Choose one of these actions:
- Allow edit: Editing of the table, form, or record is allowed.
- Lock edit: Editing of the table, form, or record is locked.
  In the Default action field, select an option.
10. You can (temporary) stop applying the table setup record. So, when the field security policy is applied, the table setup record is skipped.
  Select the Skip check box.
11. Sub-task: Define company group.
  11.1 You can apply a table setup record to one or more company groups. So, the table setup record is only applied to the companies that are defined in the company group.
If no company group is defined for a table set up record, it is applicable to all companies in the D365 FO environment.
  In the Table setup section, in the list, find and select the desired record.
 

Note: You can define the applicable company groups as well when you apply a form mapping to a field security policy.

  11.2 Click Company group.
  11.3 Click New.
  11.4 In the Company group field, enter or select a value.
  11.5 Close the page.

Notes

You can only edit an inactive field security policy.

Related to Notes

Edit field security policy

 

Provide feedback