web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Dynamics 365 (CRM) Import - Multi-Select Option Set Field Fails

(2) ShareShare
ReportReport
Posted on by 15

Seems 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"

image

Multi-Select Option Set

image

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 (2)
  • Suggested answer
    Tom_Gioielli Profile Picture
    3,084 Super User 2026 Season 1 on at
    Multi-select option sets are the bane of my existence. 
     
    How are your values being stored in the import file? I believe the format should be the following for multi-select.
     
    option 1; option 2; option 4
     
    Is there any mapping in the import file dialog that allows you to define specific values? A bit more information might help us figure out how to get you past the finish line here.
  • BB-30101906-0 Profile Picture
    15 on at
    Hi Tom,
     
    In this particular case, we export the data directly from CRM, make updates, and import the data back into the CRM.  The values are being stored in the same way the data was exported from Dynamics 365 (as shown above with ";" as the separator).  The import still fails with the message that the "source data is the wrong format" even if I don't modify any of the "multi-select option set" fields.  Same result with .xlsx or .csv file.
     
    It doesn't appear there is any option in the mapping step other than to select the fields to map between the CRM and import file.  Given that the import file is the same file that was exported, it auto-maps anyway.
     
    Not sure what else to try at this point.
     
    Thanks.
     
     
     
     
     
  • Suggested answer
    Tom_Gioielli Profile Picture
    3,084 Super User 2026 Season 1 on at
    OK, I got this to work but you probably won't like how I had to do it. Before we get to how it worked, let me outline a few things that did not work for me.
    • Replacing the labels of an option set with the integer values with an excel import
    • Replacing the labels with integers, and replacing the semi-colon with a comma with an excel import
    • Removing extra spaces with both of the above formats with an excel import
    • Trying the new Preview import feature from directly on the table in make.powerapps.com
    • Cursing quietly at my computer screen and threatening it until it imported properly
    • A few more random formatting things
    In the end, I could not get it to work through the excel import no matter what I tried. Unless I'm missing something, that's a dead end. 
     
    ----------------------------------------------
    So, I decided to move over to Power Automate to see what I could do there and if I could update a Multi-Select field. The answer is YES, but the formatting is wonky. After a bunch of errors, I decided to just do a "Get a Row" action so I could see how multi-select fields were being stored and referenced in a flow.
     
     
    ----------------------------------------------
    As you can see in the screenshot, it was storing it with the option set values separate by a comma. I tried putting that directly into a step to update this field in another record, like so.
     
    This did not work, and I got the error that the values being passed in were not integers. Passing them in with quotes around obviously didn't work either.
     
    ----------------------------------------------
     
    I finally was able to make it work by using the formula input to convert both fields to integers and separating them with a comma. You basically need to force the field to accept both the option set values as integers but still include the comma separating each value.
     
    This ran successfully for me, and it added both choices to my option set. Hopefully this gets you far enough along that you can write a flow that reads your updated excel file, build out the update value as needed based on the selected values, and updates it according to this format. Unless or until someone comes along who knows a different and hopefully easier way to do it, I can confirm that this at least worked for me.
     
    ----------------------------------------------
    Good luck and let me know if this works out or you find an easier way.
  • Tom_Gioielli Profile Picture
    3,084 Super User 2026 Season 1 on at
    @BB-30101906-0 any luck on this? Were you all able to get this sorted out through Power Automate or some othe rmethod?
  • BB-30101906-0 Profile Picture
    15 on at
    Sorry for the delay.  I have not had a chance to validate your suggestion but will hopefully have some time later this week.  I fear it would not be a suitable long-term solution.  I have to believe this is a bug and Microsoft will eventually correct the issue, but if it is by design, we may choose to change the field type in the CRM to work around it.  I'll update the thread soon...
  • Suggested answer
    Tom_Gioielli Profile Picture
    3,084 Super User 2026 Season 1 on at
    @BB-30101906-0, another user provided an answer to this in another thread.
     
     
    Looks like the choices need to have the leading space removed before attempting to reimport. I just did a quick test and confirmed that it worked.
     
    Does NOT Work
    option 1: option 2; option 3
     
    Works with Mapping
    option 1;option 2;option 3

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 156

#2
Pallavi Phade Profile Picture

Pallavi Phade 102 Super User 2026 Season 1

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 55 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans