The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We had an annoying error, we tried to import a solution with a new field on the case table. The case table already had 300 plus fields on it so it was a bit a mammoth table.
Whilst trying to find the problem we split the various enhancements into separate solutions in an attempt to make each separate solution smaller and increase the chances of smaller solutions importing rather than one big one.
The reason we split up the solution was because we thought the problem was a timeout issue.
Interestingly the solutions with workflows and plugins imported. The solutions with other entities included also imported and we were left with a solution with just the case entity in which was still refusing to import.
The changes in the solution were minimal, we were basically adding one new field to the case entity but I guess this is adding a new field and value to all the case records which already exist in CRM database.
I remembered I previously had problems importing a large solution, so I searched my blog and found this
CRM 2011 – A time-out occurs when you import a solution in Microsoft Dynamics CRM 2011
In the blog I also refer to this KB article about a timeout when importing solutions
We were pretty sure the import was timing out because it was taking too long to import, so we increased the OLEDBTimeout and the ExtendedTimeout and this allowed the import process more time to import the solution and finally it worked.
A good reason to write blogs is you might run into the problem again later and if you have blogged about it you can easily find the solution to your problem even when you have forgotten the solution yourself.
I imagine this solution and the two registry keys would probably still be used in CRM 2013 although I haven’t tried this out yet.
Business Applications communities