Activities

To apply a field security policy, you must activate it.

Once a form mapping for a field security policy is recorded and review is finished, you can apply the form mapping to the field security policy. If you do so, all form mapping records, of the same field security policy as the selected form mapping record, are applied.

For each form mapping record, this data is copied to the field security policy:

• Table name (Data source name)
• Form name (Only if the Create form specific setup field is set to 'Yes')
• Table field name, control name, or Dimension name

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.

You can use a dynamic query to define the data in the database to which a field security policy applies.

You can link a dynamic query to a condition that is applied to a field security policy.

This topic explains how to set up a dynamic query with the Query wizard.

You can also start the dynamic query wizard from an existing query to edit it.

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

This topic explains how to create a field security policy.

Use field security policy versions to manage changes on field security policies.

You can create a new field security policy version, for example, if you have an active version and want to make changes to the field security policy. In this case, create a new version, based on the active version, and make the changes in that version.

You can use a function to fill the value of a condition on a query range.
For a function, a class is required. To develop this class, extend the DQFFunctionRun class.
Prerequisite: Develop the extension of the DQFFunctionRun class in the AOT before you start the steps.
The steps in this topic are to have the developed function class uploaded as function.

When a field security policy is exported in the background, the created XML file is stored in Download transactions. You can download the XML file to your local download folder.

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:

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:

You can export a field security policy to an XML file. With this file, you can import the field security policy in another D365 FO environment.

This topic explains how to export a field security policy to a file.

This setup is included in the export:

• The selected field security policy with the table setup, field setup, and condition setup.
• All versions or a specifically selected version of the field security policy.
• The linked company groups. The companies as defined in the company groups are not exported.

You can export a field security policy to an XML file. With this file, you can import the field security policy in another D365 FO environment.

This topic explains how to import a field security policy from a file.

This setup is included in the import, depending on the contents of the file:

• The field security policy with the table setup, field setup, and condition setup.
• All versions or a specifically selected version of the field security policy, depending on what is included in the file.
• The linked company groups. The companies, as defined for the company groups in the export environment, are not included in the import.

Use the form mapping to define which tables, forms, and fields you want to include in the field security policy.

For a specific field security policy, you can record the relevant form mapping.

When recording, you can record several forms. For each form that you record, a separate form mapping record is created.

Use the form mapping to define which tables, forms, and fields you want to include in the field security policy.

To create a form mapping, you record it. The recording results are stored in the Form mapping table. You can review and edit the recorded form mapping. Usually, you only delete undesired recorded fields from the form mapping. To add a field to the form mapping, record it.

Use field security policy versions to manage changes on field security policies.

If several versions exists of a field security policy, you can select which version is shown on the page.

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: