Disabling Mappings

On the row of the relevant mapping, click, then Disable to disable custom mappings. Your changes will be saved automatically. When a mapping is disabled, data from the source field will not be transferred to the target field. It might not be possible to disable mappings if your custom mappings are stored outside of Foundations.

Either of the following four statuses appear next to each mapping in hierarchical order:

  • Enabled
  • Disabled
  • Overridden
  • Parent Overridden

The mapping is not in use if it has a status of Disabled, Overridden, or Parent Overridden.


Only custom mappings can be disabled. By default, they are all enabled.

If a disabled custom parent mapping has child mappings, these are also disabled. If one of the child mappings gets re-enabled, so will the parent mapping, but not the rest of the children. If a parent mapping is enabled, all of the child mappings will also be enabled.

When creating a child mapping on a disabled parent mapping, the child mapping’s enablement status will automatically be Disabled.


Depending on the predefined configuration for a set of mappings, you will not have the ability to disable or override mappings. If you do not have the ability to disable mappings, the Status column will be hidden.

The FDN Mappings Component will display all mappings, including disabled ones.