Description Mapping Removed but variable still mapping to Description

tahnalos
Kilo Sage

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?

1 ACCEPTED SOLUTION

Nick Parsons
Mega Sage

I have noticed that mapping will also occur if the Name field of the Description variable is the same as the name of the description in the backend incident (so if you have description as the name, then it will map). If you change the variable's Name it should no longer map (but also keep in mind potential locations that might be relying on that variable's name, such as scripts). 

View solution in original post

7 REPLIES 7

Medi C
Giga Sage

Hi @tahnalos,

is there any template applied?

can you share screenshots from your description field as well as the record producer script?


If you found this helpful, please hit the thumbs-up button and mark as correct. That helps others find their solutions.

As far as I can tell, there is no template.  The scripts that I have seen on the record producer itself do not touch the description field, and there appears to be no business rule that does this either.

Hi @tahnalos,

 

Could you please run the following script in "Scripts - Background" and try again (Update the sys_id with the description sys_id):

var current = new GlideRecord("item_option_new");
if (current.get("87372a2553402300afffddeeff7b1253")) { //Update with "Description" sys_id
    gs.info("MAPPED FIELD before update: " + current.field);
    current.setValue("field", "");
    current.update();
    gs.info("MAPPED FIELD after update: " + current.field);
}

 

The second info message should be only"

MAPPED FIELD after update:

 


If you found this helpful, please hit the thumbs-up button and mark as correct. That helps others find their solutions.

Nick Parsons
Mega Sage

I have noticed that mapping will also occur if the Name field of the Description variable is the same as the name of the description in the backend incident (so if you have description as the name, then it will map). If you change the variable's Name it should no longer map (but also keep in mind potential locations that might be relying on that variable's name, such as scripts).