Skip to content
English
More Support
Contact Us
  • There are no suggestions because the search field is empty.

Data Synchronization Failure Causes

Data Synchronization Failure Causes

Data synchronization (“data sync”) failures occur when:

  • The system sending the data experiences a failure when attempting to send
  • The system receiving the data fails to receive it
  • The system receiving the data receives it in a format that it has defined as unaccepted


Sync Failure: Uniqueness Keys


Get to Know Your Uniqueness Keys


Why are uniqueness keys important?

  • Uniqueness keys allow RepSpark to create a data record for a table that can be distinguished from other records - in other words, the record is unique. A combination of fields is used to determine this uniqueness. Below is a list of fields that are considered, in combination, to produce a unique record for Order and Invoice Reports
  • When a new data record is NOT unique from other, existing records, RepSpark flags the record as a duplicate. At best, duplicate records are not processed. At worst, they cause a data sync error, and the sync process cannot be completed.

Great, but where do I find my data’s uniqueness keys?


  • Log into your site and go to Admin -> Uniqueness Keys to see the way RepSpark defines uniqueness for all of your data objects.

  • For additional information on required API fields on developers.repspark.com.
  • Ask your Account Manager or Professional Services Consultant to supply a mapping document for your data.

Sync Failure: Required Fields

What is a required field?

  • Required fields are data elements that are required for RepSpark to either a) distinguish a unique record, or b) enable users to place an order.
    • The Uniqueness Keys section above covers how to prevent sync failures due to duplicate records
    • This section will focus on fields that are required to avoid data display and order export errors

How do I know which fields are required in my data?


  • Ask Support, your Account Manager, or your Professional Services Consultant for your brand’s mapping documentation, which includes required fields
  • If using flat files, refer to our flat file mapping documentation - also available from Support, your Account Manager, or your Professional Services Consultant

Sync Failure: Large API Data Sets


  • RepSpark recommends that API developers use Begin, Append, and Commit when syncing more than 1,000 records in a transaction. Otherwise, you can omit the batch type header and make a single API request.

Sync Failures: Maximum Data Length