Share
Report
5Seems Microsoft changed the way imports are done in Dynamics 365. In the new workflow, fields that are type "Multi-Select Option Set" fail during import with a message that the source data is the wrong format. This new import approach must have been released within the last 3 months.
I notice that during the field mapping step, the system may not be detecting the field type correctly. Below you can see how standard "Option Set" fields have a designation, yet I don't see that associated with multi-select option set type fields.
Standard "Option Set"
Multi-Select Option Set
Not sure the above has any relevance to the issue but thought I would mention it.
Has anyone else run into this?
Thanks.
Categories:
I have the same question (0)
All responses (
Answers (
