Trying to export Common Data Services Default Solution (unmanaged) to import into a new environment so I can migrate CDS customizations. This is the only error I get:
A failure occurred while exporting the solution. An unexpected error occurred.
Followed the steps here
https://docs.microsoft.com/en-us/power-platform/admin/environment-and-tenant-migration
I've tried Publishing all changes. I also tried to run the solution checker, that also fails.
Any thoughts?
Hi @mike528 ,
The failure to export a large solution from the Common Data Service environment probably because a timeout exception on the export request.
The workaround is to create smaller solutions with fewer components to be analyzed. If the large file size of the solution is due to many plug-in assembly components, please see guidance to Optimize custom assembly development.
Best regards,
Sik
@v-siky-msft
I don't get a timeout, I get an unexpected error. The only components in my Common Data Services Default Solution are the entities that I created and/or customized and my custom option sets. A total of 28 items. If this is too big then no-ones should work.
Thanks
As you're not getting a useful error, I think you're best contacting Microsoft Support. The only other would be to create a new solution, and progressively add the components to this solution and try exporting them to see which component causes the error (or if you get the error with any component, then that would indicate a problem with the overall environment)
@DanW
Would love to, where do i find it? The only message I get is shown below.
Unfortunately I cannot see your attachment thanks to our InfoSec team, but typically there is a button that says Download Log File. Another thought I had is, you said you were trying to do this to the default solution, and that there where not a lot of customizations. Have you tried creating a new solution, and just pulling in the entities and resources you need, then exporting that solution?
I have test form my side, CDS Default solution of some environments can be exported, but some cannot. After I removed some components, it works now.
Could you try to remove some components that you don't need from the solution? Or could you try to create a new solution, add the components you need , and check if it can be exported?
Yes, have seen this - found a connector for Dataverse in an app (unused) developed over time (is a larger but one change on a button on select (simple) lead us to this issue randomly). Removed that connector and the solution exported. Seems to be related to Dataverse/CDS, perhaps in solutions where you have previous links. Also to note MS have been updating features for Dataverse connectivity (environment variables for example - auto populating), may relate?Worth noting here in case any one else has same issue to come back to same issue.
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.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 836 Most Valuable Professional
Michael E. Gernaey 327 Super User 2025 Season 2
MS.Ragavendar 231 Super User 2025 Season 2
