Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
Prior to PU21, if a SQL transient error occurred, an error will be thrown in X++ and there was no way to identify and catch it.
Starting from PU21, instead of throwing an error, an exception will be thrown with the type (TransientSqlConnectionError). This will give you the ability to catch and retry your outermost transaction in X++.
Before the exception was thrown, the AOS (kernel) has already retried the connection if the query is not within a transaction, hence you can use this exception and do your retries.
We recommend that you limit the number of retries so your code doesn’t get stuck if the Database takes longer time to recover.
For more details please see here
public static void LargeTransactionWrapper()
info("Caught transient SQL connection error, ttslevel=" + int2Str(appl.ttsLevel()));
// At this point, transaction is canceled
// Code that indicates retry is possible
// Do clean up
Business Applications communities