Data Source xls Import is not updating choice value as expectedIssue During xls imports from one ServiceNow instance to another, when using a "transform map" the data is getting updated in the target table but with unexpected errors. For example, the sys_choice table values are updating some values as per the choice list as expected, while some are not working correctly and do not get updated. Or unexpectedly new records are being created where the expectation was that "coalescing" would update a record rather than create a new one.CauseDuring the import some of the Source fields are possibly "truncated" or contain incorrect data, resulting in the instance not being able to match it to a "Sys_choice" entry in sys_choice_list. Or not being able to coalesce it on a "different" target table field resulting in the creation of a new record instead of "updating" it as expected.ResolutionMake sure that the "correct data" is being imported to the target field. In some cases, the ServiceNow instance target field is NOT intended for the imported data type, simply due to an error in the creation of the transform map matching an incorrect field. However, there are examples that happen for different reasons: For example, Sys_user.country is intended to be used by specific sys_choice entries that are present out of box (OOB). An OOB instance would never be longer than "3" characters as it would contain a country. If the customer is importing "larger" string data into this field, that would by default result in truncated data. And not match the sys_choice entry associated with the sys_user.country field (which can have a much higher value of 4000). So even if the sys_choice list associated with sys_user.country contains data that would contain a larger string, it cannot be matched. In this case, it could be wise to match the "Max length" entry in the sys_dictionary entry of the target associated with the table. This is so that during the import, the system can appropriately match the imported data. Please note that all changes to sys_dictionary should be extensively tested and not be suggested before speaking to a platform technology engineer or the appropriate development team.