SLAKPI Instance trigger for Status Changed, gets fired twice on Near Non-Compliance

(0) Share

Report

Posted on by gzouganelis

Hi all,

Similarly to what Neil Parkhurst describes in his post ((+) Dynamics 365 Customer Service SLAs and Cloud Flows - Microsoft Dynamics CRM Community), we have created a trigger on SLAKPIInstance records for `status` field modification:

We have only one active SLA for testing, with 2 SLA Items, 1xFirstResponseBy and 1xResolveBy with a default Action flow on each of them:

Having a minimal configuration with no extra flows/triggers messing up with writing to SLAKPIInstance records,
the trigger gets fired twice when status is changed to 'Succeeded'(4) or 'Nearing Noncompliance'(2), in both First Response By/Resolve by KPIs SLA Items,
while when 'Noncompliant'(1), gets fired once. (Haven't tested Paused/Canceled as they are not monitored in our case)

Any hints plz?

NOTE: If placing the Manual action call of the trigger into the default Action flows (without any triggers), everything works ok.

I have the same question (0)

All responses (2)

Answers (0)

gzouganelis 5 on at

Like (0)

Report

RE: SLAKPI Instance trigger for Status Changed, gets fired twice on Near Non-Compliance

Hi Nya,

the flow is the default flow which is created when clicking the "configure actions" in a SLA item, thus

every branch in the switch is empty, checks for 1,2,4 status with no actions:

Was this reply helpful? Yes No
Nya 29,060 on at

Like (0)

Report

RE: SLAKPI Instance trigger for Status Changed, gets fired twice on Near Non-Compliance

Hi,

Would you please provide a screenshot with expanding the "Switch" step?

Was this reply helpful? Yes No