Default
The Default action is used when mapping a field that should write a default value to the Target field. For example, if the Target field should always contain the value “1,” create a rule that populates the field with this default value for every record that is mapped.
To create a field mapping using the Default action on the Field Mappings page:
-
Select the field to be mapped.
-
Click Edit.
-
Select Default from the ACTION list box.
-
Enter the default value to write to the Target field in the DEFAULT field.
NOTE: While mapping a field with the Default action, a user can create a placeholder to create output values for blank, empty, and null values. The rule created by the mapping uses these output values. If the user enters <blank> in the Default field on the Field Mappings page, the output used in the rule is single quotes with one space between them (’ ‘). If the user enters <empty>, the rule uses single quotes with no space between them (''). If the user enters <null>, the rules uses NULL, representing no data.
-
Click Save.
-
Click the Submit icon on the Page toolbar.
NOTE: If the Auto Gen Level on the Automation page’s Vertical View is set to Off for the Target, this rule is not built in SQL. If the Auto Gen Level is set to ON but the Auto Generate Rule check box on the Automation SQL Field Mappings page’s Vertical View is unchecked, then the rule is not built.
The mapping must be approved by a Developer on the Mapping Approval page for documentation purposes and to help track progress of the data migration project. Refer to Approve or Reject Mappings and Assign Developers to a Target or Source for more information.
Once the mapping has been submitted, the Action, Source Table, Source Field and Default Value fields do not allow updates until one of the following events occurs:
- The Developer clicks Reject on the Mapping Approval page.
- The Mapper clicks Reset on the Field Mappings page.
NOTE: When a user clicks Reset, Mapping By, Submitted By, Created By and Approved By field will be reset to NULL values. The Rejected By field does not update and contains the user ID of the Developer who rejected the mapping on the Mapping Approval page. The Mapper can contact the Developer with any questions.
Once the fields allow update, edit them, click Save, and click the Submiticon on the Page toolbar. This updated mapping is sent to the Developer for review on the Mapping Approval page.
Was this article helpful?
Sorry about that.
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
Want to tell us more?
Send an email to our authors to leave your feedback.
Great!
Thanks for your feedback.