Description Mapping Removed but variable still mapping to Description

[tahnalos]

Hello

We had created a Record producer to the Incident form.  Amongst the variables for this Record Producer, is a Description field which was mapped to the Description field on Incident.  During meetings regarding this functionality, it was determined that the Description field on Incident needs to be a different value, so the mapping link was removed.  But despite this happening, the mapping is still occurring.  We suspect that someone may have introduced code in a separate effort to match fields but we can't track this code down.

We checked the scripts coming from the Record Producer, and nothing is touching the Description field.  We also checked the business rules on Incident, and did not notice any scripting that may be copying value from the Variable Description to the Incident Description.

Is there any other locations that we need to be looking at?

[tahnalos]

Could there be a property that automatically maps a variable description field to the form description field?

[Nick Parsons]

Potentially, but I haven't found anything in the docs around this - but this is OOTB behaviour, if your Name of the variable is currently description, then that would be why the auto-mapping is occurring.

The mapping that takes place between a variable and a field in a table takes place if the variable name matches a field name in the table

---

- In record producers, variables in variable sets are not passed to the matching field on the record -...

[tahnalos]

Thanks.

Whoever designed these record producers used the "description" name a bit too much.  All of these record producers were discovered to have the same exact problem.  Granted, they are supposed to be mapped to the description field on the target table, but we're thinking that this should not have been done.

Thanks