Disabling Mappings

You can disable a custom mapping by clicking on the row of the relevant mapping, then clicking Disable. Your changes are saved automatically. You can also disable custom mappings in the edit window of a custom mapping by selecting Disable in the Status field, then click Save. When a mapping is disabled, data from the source field will not be transferred to the target field. Disabling mappings might not be possible 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

A mapping status prefixed with 'Managed -' indicates that the mapping is managed. Managed mappings cannot be disabled, but can be overridden by other mappings.

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

Note:

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.

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