Skip to content

Commit a5eae78

Browse files
authored
4 articles
1 parent 2959060 commit a5eae78

File tree

5 files changed

+211
-1
lines changed

5 files changed

+211
-1
lines changed
Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
title: Service Activity Not Visible and Missing Book Button
3+
description: Solves an issue where the Book button isn't available for service activities and service activities don't appear under Unscheduled Service Activities in Microsoft Dynamics 365 Customer Service.
4+
ms.reviewer: ghoshsoham
5+
author: Yerragovula
6+
ms.author: srreddy
7+
ai-usage: ai-assisted
8+
ms.date: 04/17/2025
9+
ms.custom: sap:Core Service Scheduling, DFM
10+
---
11+
# Book button isn't available for service activity and Unscheduled Service Activities doesn't show service activities
12+
13+
This article provides guidance on resolving the issue where the **Book** button isn't available for service activities, and service activities don't appear under the **Unscheduled Service Activities** view in the [schedule board](dynamics365/customer-service/use/use-schedule-board-configure-service-activity) in Dynamics 365 Customer Service.
14+
15+
## Symptoms
16+
17+
You might encounter the following issues in Dynamics 365 Customer Service:
18+
19+
- The **Book** button is missing for service activities.
20+
- Service activities aren't visible under the **Unscheduled Service Activities** view in the schedule board.
21+
22+
## Cause
23+
24+
This issue may occur due to one of the following reasons:
25+
26+
- The entity isn't enabled in the **Resource Scheduling** settings.
27+
- Post-import code didn't execute properly for service scheduling upon import. This code is essential for enabling service appointments for scheduling and establishing additional relationships.
28+
29+
## Resolution
30+
31+
To resolve the issue,
32+
33+
1. Open the **Resource Scheduling** app in Dynamics 365.
34+
2. Select **Settings** in the navigation area.
35+
3. Select **Administration** from the site map.
36+
4. Select **Enable Resource Scheduling for Entities**.
37+
5. Verify if the relevant [entity](/dynamics365/customer-service/administer/scheduling.entities#understand-scheduling-entities) is enabled. If it isn't enabled,
38+
39+
1. Enable the entity.
40+
2. Publish the changes.
41+
42+
If the issue persists, it may be caused by post-import code not executing properly. To solve this issue:
43+
44+
1. Check for available updates for the Dynamics 365 Service Scheduling solution.
45+
2. Apply the updates as per the instructions provided. For more information, see [Manage Dynamics 365 apps that run on Microsoft Dataverse](/power-platform/admin/manage-apps).
Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: Can't Install Customer Service Apps In Existing Environment
3+
description: Solves an issue where users can't install Dynamics 365 Customer Service applications in an existing Power Platform environment.
4+
ms.reviewer: ghoshsoham
5+
author: Yerragovula
6+
ms.author: srreddy
7+
ai-usage: ai-assisted
8+
ms.date: 04/17/2025
9+
ms.custom: sap:Core Service Scheduling, DFM
10+
---
11+
# Can't install Dynamics 365 Customer Service applications in an existing Power Platform environment
12+
13+
This article provides guidance for users encountering issues while trying to install Dynamics 365 Customer Service applications, such as the Customer Service workspace and Customer Service admin center model-driven apps, in an existing Power Platform environment.
14+
15+
## Symptoms
16+
17+
Users can't install Dynamics 365 Customer Service applications in an existing Power Platform environment, such as the [Customer Service workspace](/dynamics365/customer-service/implement/csw-overview?tabs=customerserviceadmincenter) and the [Copilot Service admin center (previously known as Customer Service admin center)](/dynamics365/customer-service/implement/cs-admin-center) model-driven applications.
18+
19+
This issue occurs due to one or more of the following reasons:
20+
21+
## Cause 1: The environment is Dataverse-only
22+
23+
- The environment is created as a Dataverse-only environment without enabling Dynamics 365 apps.
24+
- Dynamics 365 applications, such as Customer Service workspace, require the environment to be created with the **Enable Dynamics 365 apps** option selected during the environment setup.
25+
- The **Enable Dynamics 365 apps** option allows the environment to host first-party applications such as Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Marketing.
26+
27+
### Resolution
28+
29+
1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
30+
2. Select the environment where you are trying to install the applications.
31+
3. Go to **Settings** > **Overview**, verify whether the environment is listed as **Dataverse-only** or if Dynamics 365 apps are enabled.
32+
33+
## Cause 2: Missing or incorrect licensing
34+
35+
Users trying to install or access Dynamics 365 applications must have the appropriate license assigned. For more information, see [Customer Service Pricing](/dynamics-365/products/customer-service/pricing).
36+
37+
### Resolution
38+
39+
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com/).
40+
2. Select **Users** > **Active users**.
41+
3. Locate and select the user who needs access to the Customer Service applications.
42+
4. Select **Licenses and apps**, and ensure the user has one of the following licenses assigned:
43+
44+
- Customer Service Professional
45+
- Customer Service Enterprise
46+
- Customer Service Premium
47+
48+
5. Save the changes.
49+
50+
## More information
51+
52+
If the current environment isn't configured to support Dynamics 365 applications, follow these steps to create a new environment:
53+
54+
1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
55+
2. Select **+ New environment**.
56+
3. Provide a name and select a region for the new environment.
57+
4. Under **Type**, select **Production** or **Sandbox** as required.
58+
5. Enable Dataverse by selecting the appropriate box.
59+
6. Enable Dynamics 365 apps by selecting the **Enable Dynamics 365 apps** checkbox.
60+
7. Select **Save** and wait for the provisioning process to complete.
61+
62+
Once the environment is successfully set up, the [Customer Service Hub](/dynamics365/customer-service/implement/customer-service-hub-user-guide-basics) and Copilot Service admin center applications will be available in the app list for users with the appropriate licenses.
63+
64+
For more detailed guidance on creating and managing environments, see [Create and manage environments in the Power Platform admin center](https://learn.microsoft.com/en-us/power-platform/admin/create-environment).
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: Agents Don't Receive Desktop Notifications For New Messages
3+
description: Solves an issue where agents don't receive desktop notifications for new session messages when the browser isn't active in Microsoft Dynamics 365 Contact Center and Dynamics 365 Customer Service.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ms.reviewer: courtser
7+
ai-usage: ai-assisted
8+
ms.date: 04/17/2025
9+
ms.custom: sap:Live chat Widget (LCW), DFM
10+
---
11+
# Agents don't receive desktop notifications for new session messages when the browser isn't active
12+
13+
This article addresses an issue where agents don't receive notifications for newly assigned session messages when their browser page isn't actively viewed in Dynamics 365 Contact Center and Dynamics 365 Customer Service.
14+
15+
## Symptoms
16+
17+
Agents don't receive [notifications](/dynamics365/customer-service/administer/notification-templates#desktop-notifications) for new session messages when the browser is running in the background.
18+
19+
## Cause
20+
21+
This issue occurs because the system is configured to use default notification templates, which don't support desktop notifications when the application isn't actively in use.
22+
23+
## Resolution
24+
25+
To resolve this issue and enable desktop notifications for agents when the browser isn't active, follow these steps:
26+
27+
1. Create a new notification template:
28+
29+
- Navigate to the [notification settings](/dynamics365/customer-service/administer/notification-templates#create-a-notification-template) in the Dynamics 365 environment.
30+
- Create a notification template named "When app is in the background."
31+
- Enable the **Show Desktop Notification** setting for this template.
32+
33+
For more information, see [Use notifications in Dynamics 365 Customer Service](/dynamics365/customer-service/use/oc-notifications).
34+
35+
2. Associate the newly created notification template with the appropriate workstream:
36+
37+
- Identify the workstream(s) that require the new notification template.
38+
- Associate the "When app is in the background" notification template with the relevant workstream(s).
39+
40+
For step-by-step guidance, see [Associate notification templates with workstreams](/dynamics365/customer-service/administer/associate-templates).
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: Queue Email Address is Unresolved or Unrecognized In the To Field
3+
description: Solves an issue where emails sent to a queue show the queue email address as unresolved or unrecognized in the To field in Microsoft Dynamics 365.
4+
author: Yerragovula
5+
ms.author: srreddy
6+
ms.reviewer: courtser
7+
ai-usage: ai-assisted
8+
ms.date: 04/17/2025
9+
ms.custom: sap:Queues, DFM
10+
---
11+
# Queue email address isn't resolved correctly in Dynamics 365
12+
13+
This article addresses an issue where emails sent to a queue show the queue email address as unresolved or unrecognized in the **To** field in Dynamics 365.
14+
15+
## Symptoms
16+
17+
When emails are sent to a [queue](/dynamics365/customer-service/administer/set-up-queues-manage-activities-cases) in Dynamics 365, the queue email address appears as unresolved or unrecognized in the **To** field within Dynamics 365. However, the system still processes the email and generates cases as expected.
18+
19+
## Cause
20+
21+
This issue occurs when multiple records within Dynamics 365 share the same email address. The system identifies multiple matches and may randomly resolve one of them. As a result, the email address appears as unresolved or unrecognized.
22+
23+
## Resolution
24+
25+
To resolve this issue, follow these steps:
26+
27+
1. Use the following [Open Data Protocol (OData) query](/power-apps/developer/data-platform/webapi/query/overview) to find duplicate email addresses in the system. This query will return all records (queues, accounts, contacts, leads, or custom records) that share the same email address.
28+
29+
`https://contoso.api.crm.dynamics.com/api/data/v9.1/emailsearches?$filter=emailaddress eq '[email protected]'`
30+
31+
> [!NOTE]
32+
> Replace the organization URL and email address in the query to fit your environment.
33+
34+
2. Remove or update duplicate email addresses:
35+
36+
1. Change the email addresses on duplicate records to ensure each email address is unique across all records.
37+
38+
2. After updating the email addresses, verify the query results to ensure duplicates no longer appear.
39+
40+
If duplicates persist in the query results, there may be a delay in the email search table refresh. Currently, there's no method to force an immediate refresh of the email search table.
41+
42+
3. Adjust Dynamics 365 system settings:
43+
44+
1. Navigate to **Advanced Settings** > **Settings** > **Administration** > **Email** in Dynamics 365.
45+
2. Locate the **Set To, cc, bcc fields as unresolved values if multiple matches are found in Incoming Emails** setting.
46+
3. Set the setting to **No** to ensure the system correctly resolves email addresses when there's only one matching record.
47+
48+
> [!IMPORTANT]
49+
> If the setting is set to **Yes**, the system won't resolve email addresses that have multiple matches. These email addresses will appear marked in red, requiring you to manually resolve them to a specific record.

support/dynamics-365/customer-service/toc.yml

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,14 @@
1616
items:
1717
- name: Troubleshoot issues using Solution Health Hub
1818
href: customer-service-insights/troubleshoot-cs-oc-solution-health.md
19+
- name: Core Service Scheduling
20+
items:
21+
- name: Service activity not visible and missing the Book button
22+
href: core-service-scheduling/book-button-not-available-for-service-activity.md
23+
- name: Customer Service Admin Center (CSAC)
24+
items:
25+
- name: Can't install applications in an existing environment
26+
href: customer-service-admin-center/cant-install-dynamics-365-customer-service-apps-in-existing-environment.md
1927
- name: Email
2028
items:
2129
- name: '"Case is missing customer" error'
@@ -47,7 +55,9 @@
4755
- name: Queues
4856
items:
4957
- name: Personal view queue filters aren't working properly
50-
href: queues/queue-filter-error.md
58+
href: queues/queue-filter-error.md
59+
- name: Queue email address isn't resolved correctly
60+
href: queues/queue-email-address-not-resolving-correctly.md
5161
- name: Service Level Agreements (SLAs)
5262
items:
5363
- name: Import, export, or upgrade SLA
@@ -176,6 +186,8 @@
176186
href: omnichannel-for-customer-service/error-create-chat-widget-social-channel.md
177187
- name: Live Chat Widget (LCW)
178188
items:
189+
- name: Agents don't receive desktop notifications for new session messages
190+
href: omnichannel-for-customer-service/agents-dont-receive-desktop-notifications-for-new-messages.md
179191
- name: Chat widget icon doesn't load on portal
180192
href: omnichannel-for-customer-service/chat-widget-icon-does-not-load-portal.md
181193
- name: Chat widget doesn't load on the portal

0 commit comments

Comments
 (0)