List field not getting updated during TransformDescriptionThe transform map has a field mapping of List fields. The transform fails to update this field when the source fields has comma separated string value that are not references to actual records on the instance.Release or EnvironmentMadrid onwardsCauseThe definition of List field as mentioned in the docs:List Reference field that accepts multiple references rather than just one.This issue is because there were changes to the GlideList field from how it was handled in the pre-Madrid releases, and users were allowed to store string values in the list field.The list field is used a reference to a list of records in a table. Therefore it is not correct to store a string value in a list field. You should store the sys_id of the records on the reference table. But in earlier releases, the GlideList field was not properly handled See problem, PRB1349190.ResolutionTo fix the issue you will have to use a String field to hold the comma separated strings instead of List. Since changing the data type on an existing field can cause data loss the recommended solution is to create a new String field, copy the value from the list to the string field. You will start using the new String field in your business logic.Additional InformationPlease see KB0752301 for additional details concerning the PRB.