Skip to main content
Dsync separates field work from the moment a server confirms it. A record can be captured locally first and synchronized later, but a local success is not the same as a server-side success.

​
What to expect

Server permissions remain authoritative. A local copy can help you keep working, but it does not grant access to a database, table, or record.

​
A safe sync check

1

Check the account

Confirm that the user is signed in and that the session has not expired.
2

Check the network

Move to a reliable connection and confirm that other network activity works on the device.
3

Check the scope

Confirm with an administrator that the account can access the database, table, and fields involved in the operation.
4

Check the result

Use the visible success, pending, or error state. If a request could have reached the server, do not blindly create a duplicate while the result is unknown.

​
When records appear stale

  1. Check the last successful sync or the message shown by Dsync.
  2. Confirm that the record is not still pending locally.
  3. Verify that the current account can access the source table.
  4. Reopen the record after a successful sync.
  5. If the value still differs, capture the record identifier and contact your administrator.

​
When a sync fails

Start with the exact error. A permission error needs an administrator; a session error needs sign-in; a network error needs connectivity; and a malformed or conflicting record may need its values corrected before retrying.
Include the account, record identifier, operation, time, connection state, and exact error text when contacting support@farmtrace.co.za.
Last modified on September 7, 2026