Hi Manish,

When mapping custom fields, ensure that these are below fields which identify the Record to Update (If updating an existing Service Request) or the Service Offering that is used to create the Service Request. This is used by ETM to determine the form to use, and so validate against Custom Fields on that form.

If the Custom Field is mapped below these fields, and the short code is valid, then please raise an Incident with our Service Desk so we can investigate this further,

On skipping fields based on other mappings, this can be done by setting the “No Value” drop down on the field to be skipped to “Skip” instead of “Use Null”. In the expression for this field, you can return a null value based on some logic (Presence of a value for another field) and this will then skip the current field.

To access previous mapped data within the same mapper, you can use “outbound”. For example, to get the value mapped earlier for the Short Code field, you can use:

outbounds"shortCode"]

For Custom Fields, this is trickier, as they are stored in a list within outbound�“customFields”]. You would need to iterate over this list to find the correct custom field and extract the value.

My suggestion would be to create a variable field, which will hold the value to go into “Field_1”, and can be easily referenced in the expression for “Field_2”. eg:
 

Kind regards,

Stephen