Set Field Visibility for Mapping
A System Administrator can set visibility for a field on the Target Fields page. Visibility determines whether fields display on the Field Mappings page in Map and can be mapped as Source fields, Target fields, or as both Target and Source fields. Visibility can also be set to None - No mapping required for the field, indicating that the field does not display on t
Visibility is useful in cases where fields must have Target Rules built but must not be Source mapped. For example, if a field always defaults to the same value, there is no need for mappers to spend time reviewing the field. The visibility is set to Target – Target only mapping and the rules are built, but the field does not display on the Field Mappings page.
In another case, a field’s visibility can be set to Source – Map Source only. The field is Source mapped, but is not included in Target Rules, so that metrics accurately reflect mappings status.
NOTE: Visibility can only be set if the field’s Target is in a Design Status of In Design.
NOTE: If the field is Natural, the visibility is set to Both – Mapping for Source and Target by default. If the field is a key zLegacy field, the visibility is set to Source – Source only mapping by default. If the zLegacy field is not a key field, the visibility is set to None - No mapping required for the field by default.
The visibility for Utility fields can also be set for columns that are appended to Target or Source tables. Refer to Allow Mapping of Utility Columns for more information.
To set visibility for a field in Target Design:
- Click Design in the Context bar.
- Click the Targets icon on the Design page.
- Click the Fields icon for a Target.
- Click the Vertical View icon for a field.
Select an option in the Visibility list box.
NOTE: Values are:
- Both – Mapping for Source and Target
- None – No mapping required for the field
- Source – Source only mapping
- Target – Target only mapping
NOTE: Natural fields cannot have a visibility set to None.
- Click Save.