Skip to content

Commit af42209

Browse files
authored
some changes
1 parent 4e398a9 commit af42209

6 files changed

Lines changed: 26 additions & 225 deletions

File tree

-36 KB
Binary file not shown.

.vs/MarchMicrosoftDocRepo/v17/DocumentLayout.backup.json

Lines changed: 0 additions & 12 deletions
This file was deleted.

.vs/MarchMicrosoftDocRepo/v17/DocumentLayout.json

Lines changed: 0 additions & 173 deletions
This file was deleted.
-1.58 MB
Binary file not shown.

.vs/VSWorkspaceState.json

Lines changed: 0 additions & 11 deletions
This file was deleted.
Lines changed: 26 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,50 +1,47 @@
11
---
2-
title: Duplicate SLA KPI instances are being created.
3-
description: Provides a resolution for an issue where the duplicate service-level agreements (SLA) KPI instance are being created.
2+
title: Duplicate SLA KPI Instances are Created
3+
description: Resolves duplicate SLA KPI instances caused by custom logic, privilege issues, or SLA items ordering in Microsoft Dynamics 365 Customer Service.
44
ms.reviewer: sdas, ghoshsoham
55
ms.author: v-heenaattar
6-
ms.date: 03/11/2025
6+
ms.date: 03/24/2025
7+
ms.custom: sap:Service Level Agreements
78
---
9+
# Duplicate SLA KPI instances are created
810

9-
# Duplicate SLA KPI instances are being created.
11+
This article explains how to troubleshoot and resolve the issue of duplicate service-level agreement (SLA) KPI instances in Dynamics 365 Customer Service.
1012

11-
12-
This article provides a resolution for an issue where the duplicate service-level agreements (SLA) KPI instance are being created.
13+
## Symptoms
1314

14-
## Symptoms:
15+
Duplicate SLA KPI instances might be created in the following scenarios:
1516

16-
Duplicate SLA KPI instances are seen been created during update of status of slakpiinstances or duplicate slakpiinstance are created at once.
17+
- During an [update of the status of SLA KPI instances](/dynamics365/customer-service/use/customer-service-hub-user-guide-case-sla#know-the-status-of-an-sla-kpi-instance-record), multiple SLA KPI instances might be unintentionally created.
18+
- Multiple SLA KPI instances are created simultaneously for the same SLA item, which might occur due to overlapping triggers or misconfigured workflows.
1719

18-
Example: When SLA is applied to a record like Case and the SLA has one slaitem created for Resolve By KPI, then when the conditions on the Case for SLA are met only one slakpiinstance for ResolveByKPI will be created. But in some cases we see duplicate slakpiinstance for ResolveByKPI been created.
19-
20-
## Cause:
20+
For example, when [an SLA is applied to a record, such as a case](/dynamics365/customer-service/administer/apply-slas), and the SLA includes an SLA item created for the **Resolve By KPI**, only one SLA KPI instance for the **Resolve By KPI** should be created when the conditions defined on the case are met. However, in some scenarios, duplicate SLA KPI instances are created for the **Resolve By KPI**.
2121

22-
Custom logic implemented by custom plugins/workflows/flows/actions.
22+
## Cause
2323

24-
## Mitigation:
24+
This issue could be caused by custom logic implemented through plugins, workflows, flows, or actions.
2525

26-
Out-of-the-box (OOB) functionality automatically creates SLA KPI instances. Hence the below customizations should be checked.
26+
## Resolution
2727

28-
1. Analyze Existing Customizations on OOB flows:
28+
By default, out-of-the-box (OOB) functionality automatically creates SLA KPI instances based on the SLA configuration and conditions defined in the SLA item. To identify the root cause and resolve issues with duplicate SLA KPI instances, check the following customizations and configurations:
2929

30-
a. Review the custom logic implemented in the SLA monitoring flow and SLA item flow.
30+
- Analyze existing customizations on OOB flows
3131

32-
b. Identify redundant triggers for creating SLA KPI instances.
32+
1. Review the custom logic implemented in the SLA monitoring flow and SLA item flow.
33+
1. Identify redundant triggers that might cause duplicate SLA KPI instances.
3334

34-
2. Validate custom plugins and workflows:
35+
- Validate custom plugins and workflows
3536

36-
a. Disable custom plugins and workflows and check if the issue is still a repro.
37+
1. Temporarily disable custom plugins and workflows to see if the issue persists.
38+
1. If the issue is resolved after disabling custom plugins, revisit and rectify the custom plugin logic causing the duplication.
3739

38-
b. In this case custom plugins logic should be revisited and rectified.
39-
40-
3. Privilege Misconfiguration:
40+
- Verify user privilege configuration
4141

42-
a. Please make sure that the prerequisites for user privileges should be met as per the SLA document here:[Configure service-level agreements in Dynamics 365 Customer Service](/dynamics365/customer-service/administer/define-service-level-agreements#prerequisites)
42+
Ensure that user privileges meet the [prerequisites](/dynamics365/customer-service/administer/define-service-level-agreements#prerequisites).
4343

44-
4. Ordering of SLAItems :
44+
- Verify ordering sequence of SLA items
4545

46-
a. Ordering of SLAItems in the SLA might also cause duplication of the SLA.
47-
48-
b. In this case, slaitems causing duplicate slakpiinstance should moved at the top in the sequence in the SLA.
49-
50-
46+
1. Review the ordering sequence of SLA items in the SLA configuration.
47+
1. If duplicate SLA KPI instances are caused by SLA item ordering, reorder the SLA items causing duplicate SLA KPI instances by moving them to the top of the sequence in the SLA configuration.

0 commit comments

Comments
 (0)