---
title: "Apply form mapping to field security policy"
slug: "apply-form-mapping-to-field-security-policy"
description: "Apply form mapping to field security policies effectively, managing company groups and batch processing for enhanced data security."
tags: ["Task topic"]
updated: 2026-03-20T11:16:17Z
published: 2026-03-20T17:44:34Z
canonical: "docs.staedean.com/apply-form-mapping-to-field-security-policy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Apply form mapping to field security policy

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

### Steps

1. Go to **Dynamic field security management** > **Policies** > **All field security policies**.

> [!NOTE]
> **Note** You can also view form mappings for all field security policies. To do so, go to **Dynamic field security management** > **Policies** > **Form mapping**.
2. In the list, find and select the desired field security policy.
3. On the **Action Pane**, click **Form mapping**.
4. Click **Form mapping**.
5. Click **Post to policy setup**.

> [!NOTE]
> **Note** If you have directly opened the **Form mapping** page, form mappings are shown for all field security policies. Before you apply a form mapping, select a form mapping record that belongs to the desired field security policy.
6. You can link a company group to a field security policy to define the companies to which the field security policy applies.

In the **Company groups** field, enter or select a value.
7. Select the version number of the field security policy to which you want to apply the form mapping.

In the **Version number** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> You can only apply the form mapping to an inactive version of a field security policy.
8. You can indicate whether the form names, as defined in the form mapping, are copied to the field security policy.

In the Create form specific setup field, select the desired option.
9. Sub-task: Set up batch processing.
  1. Expand the **Run in the background** section.
  2. In the **Batch processing** field, select an option. If **Yes**, also fill in the other fields.
  3. If desired, you can set up the recurrence.

Click **Recurrence** and fill in the fields as desired.
  4. Click **OK**.
10. Click **OK**.

> [!NOTE]
> **Notes**
> 
> - You can apply a form mapping several times to a field security policy. If you have:
>   - Recorded an additional mapping element, on apply, it is added to the field security policy.
>   - Deleted a mapping element from the form mapping, on apply, it is not deleted from the field security policy.
> - You can apply a form mapping including or excluding form specific setup. **Example:** You have applied a form mapping with **Create form specific setup** set to **Yes**. Then, you apply the same form mapping again with **Create form specific setup** set to **No**. In this case, all form mapping elements are added as new elements to the field security policy. So, you get each element twice in the field security policy, once with and once without the form specific setup.

## Related

- [Set up form mapping](/set-up-form-mapping.md)