Record Producer Map to field Peculiarities
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi all,
Not really a question but something I've stumbled across.
When creating a Record Producer variable we have the map to field checkbox. When checked it displays a "field" variable that allows the selection of a field on the target table, which in turn updates the RP variable name to be the same as the mapped field.
If the Map to field checkbox is unticked, and the variable name matches the target table field name (e.g 'short_description' on incident) then the variable is still mapped (and in the example, short_desciption is populated on the incident).
But, if map to field is ticked, but the "field" dropdown is unpopulated several strange things happen. The RP variable name is still set to short_description.
- In any portal, an HTML attribute is applied to the input: maxLength="0" - meaning the variable can take no input. (it is not set to maxlength="0" in the non-portal view of ServiceNow)
- The variable is no longer mapped on the generated record, even though the variable name and field name match (manipulation of the HTML required to add a value in the portal)
It's not very easy to tick the checkbox, and have an empty "Field" field, as ServiceNow don't have the option for -None-, but it can be done via list views and when large numbers of variables are being updated for RP's it's not uncommon to bulk update through the list view.
Anyway, thought I would share in case someone spends hours trying to debug this like I have done.