Skip to content

Commit f3f43e4

Browse files
authored
minor updates
1 parent 418c06d commit f3f43e4

File tree

6 files changed

+40
-29
lines changed

6 files changed

+40
-29
lines changed

support/dynamics-365/customer-service/core-service-scheduling/book-button-not-available-for-service-activity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,19 +5,19 @@ ms.reviewer: ghoshsoham
55
author: Yerragovula
66
ms.author: srreddy
77
ai-usage: ai-assisted
8-
ms.date: 04/21/2025
8+
ms.date: 04/24/2025
99
ms.custom: sap:Core Service Scheduling, DFM
1010
---
1111
# Book button isn't available for service activity and Unscheduled Service Activities doesn't show service activities
1212

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.
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 in Dynamics 365 Customer Service.
1414

1515
## Symptoms
1616

1717
You might encounter the following issues in Dynamics 365 Customer Service:
1818

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.
19+
- The **Book** button is missing for [service activities](/dynamics365/customer-service/use/schedule-service-activity-csh).
20+
- Service activities aren't visible under the **Unscheduled Service Activities** view in the [schedule board](/dynamics365/customer-service/use/use-schedule-board-configure-service-activity).
2121

2222
## Cause
2323

support/dynamics-365/customer-service/customer-service-admin-center/cant-install-dynamics-365-customer-service-apps-in-existing-environment.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.reviewer: ghoshsoham
55
author: Yerragovula
66
ms.author: srreddy
77
ai-usage: ai-assisted
8-
ms.date: 04/21/2025
8+
ms.date: 04/24/2025
99
ms.custom: sap:Core Service Scheduling, DFM
1010
---
1111
# Can't install Dynamics 365 Customer Service applications in an existing Power Platform environment
@@ -27,9 +27,25 @@ This issue occurs due to one or more of the following reasons:
2727
### Resolution
2828

2929
1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
30+
3031
2. Select the environment where you are trying to install the applications.
32+
3133
3. Go to **Settings** > **Overview**, and verify whether the environment is listed as **Dataverse-only** or if Dynamics 365 apps are enabled.
3234

35+
4. If the **Enable Dynamics 365 apps** option isn't enabled, that means the database was provisioned as **Dataverse-only** and you won't be able to install Dynamics 365 apps in this environment.
36+
37+
5. In this case, follow these steps to create a new environment with Dynamics 365 apps enabled:
38+
39+
1. Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/).
40+
2. Select **+ New environment**.
41+
3. Provide a name and select a region for the new environment.
42+
4. Under **Type**, select **Production** or **Sandbox** as required.
43+
5. Enable Dataverse by selecting the appropriate box.
44+
6. Enable Dynamics 365 apps by selecting the **Enable Dynamics 365 apps** checkbox.
45+
7. Select **Save** and wait for the provisioning process to complete.
46+
47+
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 are available in the app list for users with the appropriate licenses.
48+
3349
## Cause 2: Missing or incorrect licensing
3450

3551
Users trying to install or access Dynamics 365 applications must have the [appropriate license](https://www.microsoft.com/dynamics-365/products/customer-service/pricing) assigned.
@@ -39,6 +55,7 @@ Users trying to install or access Dynamics 365 applications must have the [appro
3955
1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com/).
4056
2. Select **Users** > **Active users**.
4157
3. Locate and select the user who needs access to the Customer Service applications.
58+
4259
4. Select **Licenses and apps**, and ensure the user has one of the following licenses assigned:
4360

4461
- Customer Service Professional
@@ -49,16 +66,4 @@ Users trying to install or access Dynamics 365 applications must have the [appro
4966

5067
## More information
5168

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 are available in the app list for users with the appropriate licenses.
63-
6469
For more detailed guidance on creating and managing environments, see [Create and manage environments in the Power Platform admin center](/power-platform/admin/create-environment).

support/dynamics-365/customer-service/omnichannel-for-customer-service/agents-dont-receive-desktop-notifications-for-new-messages.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: Yerragovula
55
ms.author: srreddy
66
ms.reviewer: courtser
77
ai-usage: ai-assisted
8-
ms.date: 04/21/2025
8+
ms.date: 04/24/2025
99
ms.custom: sap:Live chat Widget (LCW), DFM
1010
---
1111
# Agents don't receive desktop notifications for new session messages when the browser isn't active
@@ -18,11 +18,11 @@ Agents don't receive [notifications](/dynamics365/customer-service/administer/no
1818

1919
## Cause
2020

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.
21+
This is the expected behavior when the system is configured to use default notification templates, which don't support desktop notifications when the application isn't actively in use.
2222

2323
## Resolution
2424

25-
To resolve this issue and enable desktop notifications for agents when the browser isn't active, follow these steps:
25+
To enable desktop notifications for agents when the browser isn't active, follow these steps:
2626

2727
1. Create a new notification template:
2828

support/dynamics-365/customer-service/queues/queue-email-address-not-resolving-correctly.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,16 @@ author: Yerragovula
55
ms.author: srreddy
66
ms.reviewer: courtser
77
ai-usage: ai-assisted
8-
ms.date: 04/21/2025
8+
ms.date: 04/24/2025
99
ms.custom: sap:Queues, DFM
1010
---
1111
# Queue email address isn't resolved correctly in Dynamics 365
1212

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.
13+
This article addresses an issue in Dynamics 365 where emails sent to a queue show the queue email address as unresolved or unrecognized in the **To** field.
1414

1515
## Symptoms
1616

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.
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. However, the system still processes the email and generates cases as expected.
1818

1919
## Cause
2020

@@ -35,15 +35,17 @@ To resolve this issue, follow these steps:
3535

3636
1. Change the email addresses on duplicate records to ensure each email address is unique across all records.
3737

38-
2. After updating the email addresses, verify the query results to ensure duplicates no longer appear.
38+
2. After updating the email addresses, re-run the query and verify that duplicates no longer appear in the query result.
3939

4040
If duplicates persist in the query results, there might be a delay in the email search table refresh. Currently, there's no method to force an immediate refresh of the email search table.
4141

4242
3. Adjust Dynamics 365 system settings:
4343

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.
44+
1. Navigate to **Advanced Settings** > **Settings** > **Administration** > **Email** in Dynamics 365.
45+
46+
2. Locate the **Set To, cc, bcc fields as unresolved values if multiple matches are found in Incoming Emails** setting.
47+
48+
3. Set the setting to **No** to ensure the system correctly resolves email addresses when there's only one matching record.
4749

4850
> [!IMPORTANT]
4951
> If the setting is set to **Yes**, the system doesn't resolve email addresses that have multiple matches. These email addresses appear marked in red, requiring you to manually resolve them to a specific record.

support/dynamics-365/customer-service/other/string-or-binary-data-would-be-truncated-error.md renamed to support/power-platform/dataverse/tables-fields-and-relationships/string-or-binary-data-would-be-truncated-error.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ author: Yerragovula
55
ms.author: srreddy
66
ms.reviewer: courtser
77
ai-usage: ai-assisted
8-
ms.date: 04/18/2025
9-
ms.custom: sap:Other, DFM
8+
ms.date: 04/24/2025
9+
ms.custom: sap:Tables, Fields and Relationships, DFM
1010
---
1111
# "String or binary data would be truncated" error when deleting records from a custom table
1212

support/power-platform/dataverse/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,10 @@
180180
items:
181181
- name: Dataverse plug-ins
182182
href: plug-in-execution/dataverse-plug-ins-errors.md
183+
- name: Tables, Fields and Relationships
184+
items:
185+
- name: '"String or binary data would be truncated" error'
186+
href: tables-fields-and-relationships/string-or-binary-data-would-be-truncated-error.md
183187
- name: User permissions
184188
items:
185189
- name: Clean up inherited access

0 commit comments

Comments
 (0)