Edit input and output mapped value name in Zero Copy Connector for ERP

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Edit input and output mapped value name in Zero Copy Connector for ERP

    This guide explains how ServiceNow customers can manually edit the system-generated mapped value names for inputs and outputs when managing models in the Zero Copy Connector for ERP, specifically in the Yokohama release. This capability allows you to specify unique, meaningful names for mapped values to improve clarity and consistency in your ERP integrations.

    Show full answer Show less

    Editing Mapped Values

    • When creating or managing a model in the ERP Model Manager, mapped value names for inputs and outputs are automatically generated by the system.
    • You can manually edit these mapped value names to customize them according to your naming conventions.
    • Changes to mapped values automatically update the operation parameter values to maintain consistency.
    • If a new input or output is added, the system generates a default mapped value name that remains editable.
    • For nested child inputs, system-generated mapped values do not include the parent name, but you can manually edit these for better clarity.

    Best Practices and Considerations

    • Ensure mapped values are unique within your model to avoid conflicts.
    • If a join is used between ERP tables, any changes to mapped values should be reflected on the join fields as well to maintain integrity.
    • When the same field exists in both input and output with different mapped values, the output field’s name takes precedence.
    • You can revert to the original system-generated mapped value name at any time by removing and re-adding the field or by toggling the mapping type.

    Practical Application

    By customizing mapped value names, you gain better control and readability over your ERP model’s inputs and outputs. This flexibility helps align data mapping with your organizational standards and simplifies maintenance and updates of your ERP integrations in ServiceNow.

    Manually edit mapped value field names for input and output when managing models.

    In ERP model manager, the mapped value name in inputs and outputs is system-generated automatically. Edit the value manually as needed. Specify a unique value. You can revert to the system-generated name at any time.

    Let's step through an example. In Zero Copy Connector for ERP, create a model. For more information, see Add a new ERP model.

    On the new model, select Manage Model and add a read operation. For more information, see Add an operation to a model in Zero Copy Connector for ERP.

    On the read operation, add a read table entity, for example, on the T005 Countries table. For more information, see Add a read, update, or create entity to a model in Zero Copy Connector for ERP.

    Add entity options.

    After data is retrieved, select Specify inputs.

    Select Select mandatory inputs.

    Select Country/Region Key and select OK.

    Select mandatory inputs option.

    The system-generated mapped value is countries_country_region_key. The operation parameter value is set to the same name.

    Mandatory field with matching mapped value and required parameter fields.

    Change the mapped value to, for example, country_region_key and select Save. The updated mapped value is displayed and the operation parameter value changes to match automatically.

    Updated field with edited mapped value and updated, matching required parameter.

    If a new input is added, the mapped value is system-generated but is editable. For example, add the Nationality field and edit the name from countries_nationality to country_nationality so it's more consistent with the country_region_key name.

    New field added and mapped value is displayed as editable.

    Keep the following in mind

    • If a new child (nested) input is added, the system-generated mapped value doesn't contain the parent name. You can edit the child name for inputs and outputs. For input, the edited name is used in the operational parameter. In this example, the UDAT and BASXML_SUPPORTED fields were added and their system-generated names can be edited to contain or more closely match the parent name.

      Function call displayed with function names parent field and several child fields.

    • If a join is used, the changed name should be available on the join fields as well. For more information about joins, see Add joins between ERP tables.
    • If the same field exists in both input and output, but they have different mapped values, the name of the output field is given precedence and used.
    • If you want to revert to the system-generated name at any time, remove the field and then add it again. Another option is to change the mapping type and then change it back.