Work or School Accounts Now Enabled in Community!
On May 12 Work or School Accounts were enabled in Community, along with Microsoft accounts (MSA). This allows seamless navigation between Community, Dynamics 365 applications, and Azure Active Directory enabled sites while logged into your Work or School account.
Read more | Managing Accounts
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
We're exploring the feasibility of CRM 9 now and we have it installed in some sandbox type environments. We have an issue that I've been able to work around but I would like to know why it's happening.
In the plugin we have something that calls out to a custom service to update sales order information in our financial system. That call is fired when the plugin has an update message and the plugin depth is less than 2. When we installed CRM 9 it now seems like the plugin depth comes in at 2 instead of 1 like it used to come in in 2016. Our code has not changed, and everything should be the same instead of our CRM version.
I'm not completely certain that we weren't depending on a bug in CRM 2016 and that CRM 9 just fixed this bug. I'm just trying to find out if that's the case so that we at least have an explanation. Does anyone know if they changed the way the depth is determined in CRM 9 on prem?
As best practice, we should avoid our plugin code logic being dependent on the depth. Please see below
"Used by the platform for infinite loop prevention. In most cases, this property can be ignored. You should not take a business logic dependency on this value. The value is relative and may change without notice. It is possible for this value to be -1 or 0 within your plug-in code under certain circumstances."
I think in V9, there seems to be more platform level plugin execution for the same event before yours and that's why the depth value could have changed. Dynamics 365 is much more modular and Sales/Service/Marketing are now separate apps having their own plugins and stuff. I think this new structure could be the reason for depth change but I would enable plugin trace log and see the plugin steps executed for the same event. The trace log might give you the answer.
Personally, I would recommend you remove the dependency on the depth and only do the update if the pre and post field value conditions are met.
OK, I understand, and we will take that into consideration. Thanks for your reply.
Business Applications communities