Skip to main content

Notifications

Announcements

No record found.

Dynamics 365 Community / Forums / Dynamics 365 general forum / Couldn’t import a Cust...
Dynamics 365 general forum

Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

Posted on by 95

Attempting to import a managed Solution (exported from on premise) to cloud, I am seeing the error:

Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

Although it is not telling me that the ObjectTypeCode 10366 already exists (I see many reports of this type of problem), this may be the cause, but how do I find out what this is - there don't seem to be any clues in the log.

  • Rickards08 Profile Picture
    Rickards08 200 on at
    RE: Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

    I don't know the answer to this.

    But i've seen strange import errors that's caused by system jobs that has not been completed yet.

    One example is a solution Clean system job that runs after a solution is upgraded to version 9.

    Take a look at system jobs that waiting and manually trigger them and then try to import the solution.

    Maybe the system job started straight away for your collegue. Anyhow, I hope you find an answer.

  • Suggested answer
    Chevva Profile Picture
    Chevva 95 on at
    RE: Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

    I have done a couple of things:

    1) registered a component DLL using Plugin Reg Tool v9.

    2) tried editing the Solution by removing the entity that I thought might be causing the error. When the export failed (due to dependencies not being removed too), I simply added the entity back into the Solution and exported.

    *Now*, I can import both the 'new' Solution AND the old (failing) Solution!

    Is it possible that the plugin DLL needed to be registered first? (this wouldn't seem to be the case for my colleague who managed to load the Solution without any problems into his D365 sandbox instance (before any plugin DLL had been registered).

    BTW: using web interface across all instances.

  • Chevva Profile Picture
    Chevva 95 on at
    RE: Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

    The Solution in question has been successfully imported into another cloud instance! I didn't do this so can't easily be certain of differences between the working/failing instances.

    The logged error appears alongside a very simply entity, nothing fancy except for a small Javascript webresource handling onLoad events.

  • Rickards08 Profile Picture
    Rickards08 200 on at
    RE: Couldn’t import a CustomControl Default Config for ObjectTypeCode 10366.

    I't could be a conflict between an existing form and the one that you are trying to import.

    Maybe you use custom Controls for a field in unified interface and there is a difference between the default config between onprem and online? Maybe settings for the custom Control is not valid online?

    If you find the answer, please let us know :)

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans