Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update admin-troubleshoot-sales-synchronization.md #960

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions business-central/admin-troubleshoot-sales-synchronization.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,8 @@ The following table provides examples of typical issues:
|The permissions and roles assigned to the integration user aren't correct. | This error comes from [!INCLUDE[prod_short](includes/cds_long_md.md)] and it often includes the following text, **Principal user (Id=\<user id>, type=8) is missing \<privilegeName> privilege**. This error happens because the integration user is missing a privilege that allows it to access an entity. Typically, this error happens if you're synchronizing custom entities, or if you have an app installed in [!INCLUDE[prod_short](includes/cds_long_md.md)] that requires permission to access other [!INCLUDE[prod_short](includes/cds_long_md.md)] entities. To resolve this error, assign the permission to the integration user in [!INCLUDE[prod_short](includes/cds_long_md.md)].<br><br> You can find the integration user name on the **Dataverse Connection Setup** page. The error message provides the name of the permission, which can help you identify the entity for which you need permission. To add the missing privilege, sign in to [!INCLUDE[prod_short](includes/cds_long_md.md)] with an administrator account and edit the security role assigned to the integration user. For more information, see [Create or edit a security role to manage access](/power-platform/admin/create-edit-security-role). |
|You're coupling a record that uses another record that isn't coupled. For example, a customer whose currency isn't coupled or an item for which the unit of measure isn't coupled. | You must first couple the dependent record, for example, a currency or unit of measure, and then retry the coupling. |
|Your connection to Dataverse paused during synchronization. For example, because your session timed out. When that happens, the following error displays when you resume your session: _Table connection for table type CRM must be registered using RegisterTableConnection or cmdlet New-NAVTableConnection before it can be used._|* For session timeouts, refresh the page to reconnect to Dataverse. The error message disappears.<br><br>* For an issue in the code, for example, if you're using a custom page to show data from a Dataverse entity, contact your Microsoft partner or support. When you do, use the **Copy details** action to share details about the error. |
|User does not have required privileges (or role membership) to access the org when it is in Admin Only mode.|You can set a sandbox, production, or trial (subscription-based) environment in administration mode so that only users with System Administrator or System Customizer security roles will be able to sign in to that environment. Administration mode is useful when you want to make operational changes and not have regular users affect your work, and not have your work affect end users (non-admins).
Data synchronization will not work on Dataverse environment when in Administration mode. To disable Administration mode follow steps outlined [here](https://learn.microsoft.com/en-us/power-platform/admin/admin-mode#set-administration-mode).|

The following are some tools on the Integration Synchronization Errors page that can help you manually resolve these issues.

Expand Down