Share
Report
2When trying to import data into a dataverse environment using the Import Data-task (task: PowerPlatformImportData@2) of the Power Platform Build Tools (https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#yaml-snippet-importdata-env), the values of a Multi-Optionset attribute are ignored.
Below is a part of the data file that is generated with the Configuration Migration Tool, it includes the multi-select optionset values on the "mph_mos_portalfeature"-attribute.
<entity name="mph_serviceplanfeature" displayname="Service Plan Feature">
<records>
<record id="c3d0eac9-7be2-ed11-a7c7-0022487fe4a5">
<field name="mph_name" value="Report" />
<field name="mph_mos_portalfeature" value="[-1,19000,19001,-1]" />
<field name="mph_serviceplanfeatureid" value="c3d0eac9-7be2-ed11-a7c7-0022487fe4a5" />
</record>
...
If I import this data using the Configuration Migration Tool v4.0.0.110 (on my local machine), it does a good job and imports the Multi-select optionset values, but if I try to import it with DevOps Build Tool Import Data Task, the Multi-select optionset values are ignored (all other fields are imported successfully though).
The same issue happens if you try to import data with the Deploy Package task (task: PowerPlatformDeployPackage@2) -(https://learn.microsoft.com/en-us/power-platform/alm/devops-build-tool-tasks#yaml-snippet-deploy)
All responses (
Answers (
