Considerations for the Dynamics CRM Excel import data field type as option set

an issue that begins with the introduction of an option set field in the CRM import data first

is a property of the option set field

is the column value in Excel that I want to import, you can see that the column and field names are consistent, and the column values are not the options that are already in the option set

When you import a checksum, the option set field does not report any warning reminders as long as the field name is aligned

When the import succeeds for column values in Excel that are not in the option set, the system automatically creates

This is a hassle, so how can you avoid this problem, or how to have a reminder when the column values in Excel and the option set fields don't work, here's the workaround

Make changes to the column values by changing the column name of the previously imported Excel under the different property names of the System option set fields

A warning message appears because the name does not correspond

When you select an option set field, there is a mapping relationship so you can see the data problem at a glance

Therefore, it is recommended that when you import Excel data, the option Set field property names and columns in Excel are set to inconsistent so that when you map you will have a warning to choose manually, giving you a chance to check.

Considerations for the Dynamics CRM Excel import data field type as option set