DataSync

When attempting a Load All operation, some users receive the following error message:

Solution

These errors are caused by a database type mismatch in one of your table fields. To resolve the issue, simply remove the checkmark in the Sync column next to the problematic table (it will have a red X in the Type Destination column as shown in the image below). When re-attempting your load operation, you should no longer receive the error message.

When attempting to use DataSync for the first time after installing it, some users receive the following error message:

Solution

This error is typically happens when users have manually downloaded and installed the wrong version of .NET Core (including the SDK).

To resolve the issue:

1. Uninstall DataSync as well as all .NET Core packages that you currently have installed.

2. Restart your server.

3. Re-install DataSync. The DataSync installation process will automatically install the correct version of .NET Core which should resolve the issue.

See System Requirements for more information on DataSync installation requirements.

Sometimes, users are unable to create SharePoint connections in DataSync if dual-factor authentication is enabled in their configuration.

Solution

Remove dual-factor authentication from your SharePoint configuration by following the steps below:

1. Log in to SharePoint and navigate to the Account Settings menu.

2. In the Account Settings menu, click the Additional Security Verification option at the bottom of the Security Info pane.

   

3. Select the App Passwords option and create a new password for DataSync. Now, no double authentication will be necessary when logging in to DataSync.

   

After attempting to save a ProvideX connection, the user's UI begins looping and never saves the connection configuration.

Solution

To resolve this issue, you must change your DataSync application pool in the IIS Manager to a Windows or domain user that has access to the shared Sage 100 path.

To do so:

1. Open the IIS Manager and select Application Pools.

2. From the Application Pools list, right-click on DataSyncIdentity and select Advanced Settings from the drop-down list (shown below).
   

   

3. Locate the Process Model section and change the application pool identity from Built-in account to Custom account (as shown below). Click OK. This should resolve the UI looping issue in DataSync.
   

   

4. Repeat the above step for all DataSync application pools.

This occasional discrepancy in data synchronization may arise due to the representation of a Date field as DateTime within DataSync. When comparing two distinct data types, inconsistencies in the dates being compared can result in missing rows during the loading or deletion processes.

Solution

To fix this discrepancy, it is essential to create a custom field explicitly casting the field as a date. Subsequently, employ this customized field as your Tracking Key or Load by Partition field for a seamless data synchronization process.