Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
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
I have the below Scenario,
The case have 9 levels escalation and on each level the time is 10 minutes, however when i create and SLA with 9 SLA details and each one will fail after 10 minutes. The Workflow of the SLA will fail (on Team assign) with the message infinite loop. is there a solution for this.
In addition to the above issue, when i add the SLA to the CRM solution, and after importing it to a new organization, the assigned team will fail (red X next to the team assigned inside the SLA Detail) , even though i created the team.
Did you ever find a solution for this? I am experiencing something similar and would like to know if there is a workaround/solution for it.
The SLA detail contains a reference to the team unique identifier (GUID). Although the team's name might be the same in the new organization the GUID will be different in both systems. Thats why it will fail.
(The SDKs data migration utility might be able to copy the teams record to a new organization.)
Please check this article:
So when you say it occurs on Team assignment, you need to find out and track down how many workflows or nested child workflows could be started on the records involved.
Mine is not failing on team assignment, it fails when trying to update the original case so the next SLA detail in the chain will apply.
More detail: I have a custom field called escalation level on a case. On the first SLA failure, I set this value to 1. This will trigger the 2nd SLA detail to be applicable (This escalation level is part of the "Applicable When" criteria for each SLA detail record). When the 2nd detail fails, it sets the value to 2 which should trigger the 3rd SLA detail to come into effect. It is at this point in time that infinite loop error occurs. This is visible by viewing background processes for the case and looking at the process created by the SLA process
CRM On-premise usually allows 8 nested workflows running at max.
As a temporary workaround you can try this (but can impact system performance!):
you can't do this with CRM Online.
Do you experience this issue only when going through the escalation line very fast (within 1 hour) or whats happening if the 3rd trigger is delayed (after 1 hour) would it work with a delay of 1 hour in between?
Actually I made a workaround, I created a custom entity and when the sla fails I will created a record inside that entity with the case detail, and created a process that will assign the case to the corresponding team
I have the same problem. Did you find a workaround?
Well, thanks to Andreas and Joe D365.
Increasing the number of nested workflows did the trick.
Business Applications communities