"Solution failed to import: Couldn't import a CustomControl Default Config for ObjectTypeCode 10861"

[LozzieD]

I have exported a solution and am now trying to import it into another environment. I receive the below error message:

All the dependencies are set up. I've tried importing to different target environments, including freshly created & reset environments.

I downloaded the "log file" link on the error message:

The only references to "10861" don't seem to provide any useful diagnostic information:

I have seen these articles:

https://community.dynamics.com/blogs/post/?postid=8213060f-2670-4126-b2d1-7952a643930f 

https://passion4dynamics.com/2018/05/10/singleton-retrieve-query-should-not-return-more-than-1-recor... 

https://crmtipoftheday.com/857/missing-component-id-0-error-when-publishing-customizations/ 

But they all refer to an error message that start with the same text "Solution failed ... ObjectCodeType xxxxx" but then have some extra text on the error message to help diagnosis. My error message has no such extra text. And their remedies seem to indicate an on-premises CRM rather than Power Platform / Dataverse on-cloud, for example, using SSMS to edit the underlying database. When I point SSMS at the underlying database of the source or target environments the tables don't seem to correspond with the tables referenced in the remedies.

But still, when inspecting the databases of the source and target environments I can find no reference to 10861 as an ObjectTypeCode. Here is a query in descending order from the solutioncomponent table showing the hoighest numbered ObjectTypeCode being 10380:

I have raised a ticket with MS, but anyone any ideas?

[LozzieD]

Update: by some lateral thinking XML hackery of the customizations.xml file in the exported solution zip file, re-zipping, and then importing, I've managed to move the error message forward, if that helps anyone to help me ...

Still waiting for MS to contact me ref the open ticket.

[LozzieD · Accepted solution]

Guided by the app_import.xml error log each time the import failed, with each edit/hack of the customizations.xml in the exported solution zip file from the dev environment, re-zipping, and then importing to the test environment, one issue disappeared then revealing another one as the the import wizard continued a little further.  Rinse-and-repeat and eventually the import worked completely.

I can't remember remember all the edit/hacks now (none were documented on the internet, I just had to use the cranky error log report and follow my nose), but one stuck in my mind:

If you open the customizations.xml file in VS Code (or other editor) to make the edits/hacks, you'll likely format the xml to make it legible. That itself may add hidden characters into the xml element --like a newline at the beginning of a text between the open and close tags of an element-- which may cause the importer to fail, and not in an informative way in the error log.

Microsoft took a month to respond to my ticket, by then I'd fixed as described, so they weren't able to fast track with any method or means they may have had.

So, finally I exported the solution to a fresh environment "dev2" and tested that it exported/imported to the test environment OK (it did), and then left behind and stopped using the corrupt original dev environment.

[tfraser]

I found this thread by googling a similar error message on attempting to import a solution and found it very helpful in solving my specific problem.

My scenario is:

1. Attempt to assemble a coherent solution to move objects from a disorganised production/development environment to a fresh development environment.
2. Get stuck with errors importing relating to a single object (an entity)
3. Create a new solution containing only:
   • the entity
   • the entity metadata
   • the entity primary key column
   • the entity primary name column

When importing this bare-bones solution I had the following error:

• Couldn’t import a CustomControl Default Config for ObjectTypeCode 10373

Using the general approach suggested by @LozzieD , I had a look in the customization file in the zipped solution just using notepad and found a bit of the xml literally called 'CustomControl'.

I deleted this xml so I was just left with the parent tags.

So changed it from:

<CustomControlDefaultConfigs>
        <CustomControlDefaultConfig>
                <A LOAD OF XML />
        </CustomControlDefaultConfig>
</CustomControlDefaultConfigs>

To:

<CustomControlDefaultConfigs>
</CustomControlDefaultConfigs>

I saved the file and replaced the file in the zipped package and was then able to successfully import the bare-bones package in to the fresh production environment.

In my case I know the source table is using what I believe are relatively new custom controls applied at the table level using the old admin experience that enable editable grids and colour coding for views in a model driven app.

Maybe this isn't supported by the new environment (maybe it's not enabled for 'preview' features or something?) or the solution importer isn't capable of importing this yet?