Edit field security policy

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 this field security policy setup:

Table: 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.
Field: In the field setup, you define the fields, controls, or dimensions to which the field security policy applies. You also define how the policy is applied to the fields, controls, or dimensions.
Condition: In the condition setup, you define which inquiries or dynamic queries are applied. The conditions define how the policy is applied.

Activities

Name

Responsible

Description

Edit field security policy table setup

System administrator

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.

Change field security policy table setup sequence

System administrator

You can define the sequence in which the table setup records are applied.
Usually, in the table setup records, you can have:

One record for each table and form combination (form-specific).
One record with only the table defined and no form (table-specific).

The table setup records are applied in the sequence as defined in the table setup. The first applicable table setup record that is found, is applied.
You can have a table setup for the same table with both form-specific records and a table-specific record. In this case, you are advised to have the table-specific record applied as the last one. Otherwise, the form-specific records are not applied at all.

Edit field security policy field setup

System administrator

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, and you have edited the table setup, edit the related field setup.

In the field setup, you define the fields, controls, or dimensions to which the field security policy applies. You also define how the policy is applied to the fields, controls, or dimensions.

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.

Set up field security policy conditions

System administrator

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, and you have edited the table setup and field setup, define the applicable conditions.

In the condition setup, you define how the policy is applied.

To define a condition, you can use one of these options:

Inquiry: Use a D365 FO inquiry to define the condition.
Dynamic query: Use a query from the Dynamic query framework to define the condition.

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.

Activities

Name

Responsible

Description

Edit field security policy table setup

System administrator

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.

Change field security policy table setup sequence

System administrator

You can define the sequence in which the table setup records are applied.
Usually, in the table setup records, you can have:

One record for each table and form combination (form-specific).
One record with only the table defined and no form (table-specific).

Edit field security policy field setup

System administrator

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, and you have edited the table setup, edit the related field setup.

In the field setup, you define the fields, controls, or dimensions to which the field security policy applies. You also define how the policy is applied to the fields, controls, or dimensions.

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.

Set up field security policy conditions

System administrator

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, and you have edited the table setup and field setup, define the applicable conditions.

In the condition setup, you define how the policy is applied.

To define a condition, you can use one of these options:

Inquiry: Use a D365 FO inquiry to define the condition.
Dynamic query: Use a query from the Dynamic query framework to define the condition.

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.