Solution Properties
Solution ID:
250616100838523
Last Modified Date:
Tue Jun 16 13:08:10 UTC 2026
Taxonomy Path:
Case category//I have a problem with...//integration
Author:
[email protected]
Remote sites using Remote Data Access have different Dataset IDs
Description

Data can be out of sync for a few reasons:

  • If the Remote Data Access connection fails
  • If each computer connects to a different set of data
  • If the computers aren't using Remote Data Access at all. For example, they're connected over a local network

NOTE: If you're using Sage 50 Accounts v28 or above, refer to our alternative article.

 

If the data isn't in sync, check the Dataset IDs and if they're both N/A, follow the steps below.

Cause
Resolution

Check the Dataset ID

Check that the computers connect to Remote Data Access, and have the same Dataset ID.

To check if your computers are on Remote Data Access:

  1. When logged into your company, go to Help, then select About.
  2. In the middle column, scroll down to Remote Data Access Information.




Next to Dataset ID it will either show:

    • Main - This is the main site, where you uploaded the data to Remote Data Access. Usually where the data's held, or it's networked to a server which holds the data

    • Remote - This is a remote site and you connect remotely using Remote Data Access to the main site

    • N/A - The data isn't on Remote Data Access. This computer is accessing the data either locally or over a network

  1. If it says either Main or Remote, underneath it on the next line down, check the Dataset ID.

Both Dataset IDs are different

If one remote site has a different Dataset ID to the other, they aren't in sync because they're connected to different main sites. 

To resolve this, you need to disconnect both Remote sites, restore your backup on one computer, then set up Remote Data Access again. This results in both computers showing the same information for that company.

  1. First you must find out which computer is the Main site, using the steps in the Check the Dataset ID section above.
  2. Check which of the Remote sites have the same Dataset ID as the Main site.
  3. The steps to resync the data differ based on whether there's a Main site:

Before you do this, check if there are any transactions showing on one computer that aren't on the other.

  1. Check to see when the last time the transaction numbers had matching information. If the most recent don't match, scroll down until you find the last time the transactions matched.

    For example, transaction number 100 is the same on both sites, but then differ from number 101 onwards.

  2. You'll see one of three potential scenarios: 
▼ One computer has no transactions after the last matching transaction, the other does 
  1. Back up your data on both computers.
  2. Disconnect both remote sites from Remote Data Access for that company.
  3. Restore the most up-to-date backup on the computer to be the Main site, as a new company.
  4. Set up Remote Data Access on the computer to be the Main site.
  5. Connect to Remote Data Access as a remote site on the other computer.

They're now in sync.

To confirm this:

  • Go to Help, select About, then check the Dataset ID in the Remote Data Access Information section
▼ Neither computer has transactions after the last matching transaction 
  1. Back up your data on both computers.
  2. Disconnect both remote sites from Remote Data Access for that company.
  3. Restore the most up-to-date backup on the computer to be the Main site, as a new company.
  4. Set up Remote Data Access on the computer to be the Main site.
  5. Connect to Remote Data Access as a remote site on the other computer.

They're now in sync.

To confirm this:

  • Go to Help, select About, then check the Dataset ID in the Remote Data Access Information section

 

▼ Both computers have transactions after the last matching Transaction
  1. If both computers have different transactions after the last matching transaction, take a backup on each computer.
  2. Disconnect both Remote sites from Remote Data Access for that company.
  3. Decide which site requires the least reprocessing.
  4. Restore the more up-to-date backup onto the computer to be the Main site.
  5. Once you've restored the backup, either:
  • Manually re-process missing transactions
  • Export missing transactions from the other backup, then import them into this dataset

 NOTE: If you created any records, for example, customers, or products, on this computer, you'll need to import these before you import any transactions. 

  1. Once you have reprocessed and everything is up to date, set up Remote Data Access on this Main site computer.
  2. On the computer to be the Remote site, connect to Remote Data Access.

Once you connect the computers with Remote Data Access again, they'll have the same Dataset ID. This means that when you process on one computer information will automatically update on the other.

 

To confirm this:

  • Go to Help, select About, then check the Dataset ID in the Remote Data Access Information section

Final checks

When both computers connect to Remote Data Access, one is now the Main site and the other is the Remote site.

Confirm this and the Dataset IDs in the Check the Dataset ID section above.

 

[BCB:95:Accounts - RDA_hub:ECB]
[BCB:91:Support message - RDA / Drive chat:ECB]
Steps to duplicate
Related Solutions