You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sales-copilot/crm-permissions-and-configurations/no-changes-made-sf-ss.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ ms.author: shjais
7
7
manager: shujoshi
8
8
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
9
9
---
10
+
10
11
# "No changes were made" error when enabling Salesforce server-to-server flow
11
12
12
13
This article helps you troubleshoot the error "No changes were made." when you enable Salesforce server-to-server flow.
@@ -26,15 +27,15 @@ This article helps you troubleshoot the error "No changes were made." when you e
26
27
27
28
When you try to enable Salesforce with server-to-server flow, the following error message is displayed:
28
29
29
-
> No changes were made
30
+
> No changes were made.
30
31
31
32
## Cause
32
33
33
-
When a setup request is received, the server deploys a connected app to the Salesforce organization and creates an integration user. A permission set is then assigned to the integration user. The error occurs when the same permission set has already been assigned to the user, resulting in a duplicate assignment error during the setup process.
34
+
During Salesforce server-to-server flow setup, a connected app is deployed to the Salesforce organization. The connected app is associated with an integration user that is created automatically. A permission set is then assigned to the integration user. The error occurs when the same permission set has already been assigned to the user.
34
35
35
36
## Resolution
36
37
37
-
To resolve this issue, check for any manual changes to the connected app or profile with the prefix "Copilot For Sales." If the changes were not intentional, remove them. Try again, and contact Microsoft Support if the issue persists.
38
+
To resolve this issue, check for any manual changes to the connected app or profile with the prefix "CopilotForSales." If the changes were not intentional, revert them. Otherwise, try again and contact Microsoft Support if the issue persists.
Copy file name to clipboardExpand all lines: support/sales-copilot/crm-permissions-and-configurations/profile-name-already-exists-sf-ss.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,15 @@
1
1
---
2
-
title: The profile name is already in use. Pick a different name or rename the existing profile in Salesforce error when enabling Salesforce server-to-server flow
3
-
description: Resolves an error that occurs when the server is unable to create a new profile due to a duplicate profile name while enabling Salesforce Server-to-Server flow.
2
+
title: Profile name already in use when enabling Salesforce server-to-server flow
3
+
description: Resolves an error that occurs due to a profile with the same name already existing in Salesforce.
4
4
ms.date: 05/14/2025
5
5
author: sbmjais
6
6
ms.author: shjais
7
7
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
8
8
---
9
-
# "The profile name is already in use. Pick a different name or rename the existing profile in Salesforce" error when enabling Salesforce server-to-server flow
10
9
11
-
This article helps you troubleshoot the error "The profile name is already in use. Pick a different name or rename the existing profile in Salesforce." when you enable Salesforce server-to-server flow.
10
+
# Profile name already in use when enabling Salesforce server-to-server flow
11
+
12
+
This article helps you troubleshoot the "The profile name is already in use. Pick a different name or rename the existing profile in Salesforce." error when you enable Salesforce server-to-server flow.
12
13
13
14
## Who is affected?
14
15
@@ -25,15 +26,15 @@ This article helps you troubleshoot the error "The profile name is already in us
25
26
26
27
When you try to enable Salesforce with server-to-server flow, the following error message is displayed:
27
28
28
-
> The profile name is already in use.
29
+
> The profile name is already in use. Pick a different name or rename the existing profile in Salesforce.
29
30
30
31
## Cause
31
32
32
-
When a setup request is received, the server attempts to create a profile named **Copilot For Sales Integration Profile**for the Salesforce Server-to-Server flow. The error occurs when a profile with the same name already exists in the organization, preventing the creation process.
33
+
During Salesforce server-to-server flow setup, a profile named **Copilot For Sales Integration Profile**is created in the Salesforce organization. The error occurs when a profile with the same name already exists, thereby preventing the creation process.
33
34
34
35
## Resolution
35
36
36
-
To resolve this issue, check if a profile with the same name already exists in the Salesforce organization. If it was created before enabling the Server-to-Server flow, rename the existing profile and try again. If the profile was not created previously, contact Microsoft Support.
37
+
To resolve this issue, check if a profile with the same name already exists in the Salesforce organization. If it was created before enabling the server-to-server flow, rename the existing profile and try again. If the profile was not created previously, contact Microsoft Support.
- name: The profile name is already in use. Pick a different name or rename the existing profile in Salesforce error when enabling Salesforce server-to-server flow
0 commit comments