Resolving Entity Sync Errors with Oracle NetSuite

  • Updated

This article explains the Dependency has validation errors message you might receive while integrating Re-Leased with Oracle NetSuite. Encountering this message indicates that there are issues with related records necessary for a successful sync. These errors prevent the proper flow of data between the systems, but fret not—we'll guide you through identifying and correcting these issues swiftly.

Understanding "Dependency has validation errors"

Entities in Re-Leased, such as Contacts, Accounts, Tax Types, Invoices, Attachments, Credit Notes, Payments, and Tracking Options, all depend on one another. An error message like Dependency has validation errors suggests that one or multiple related records have validation issues—problems that occur because an entity in Re-Leased doesn't match or isn't recognized in Oracle NetSuite.

For example, syncing an Invoice that references a Contact, and if the Contact is invalid or non-existent in Oracle NetSuite, then the Invoice sync will fail. You'll need to rectify the primary issue—the dependent entity (e.g., the Contact)—before attempting to resync the Invoice or Credit Note.

Quick Solution to Resolve Validation Errors

Here's a step-by-step guide to troubleshooting and fixing validation errors for a smooth sync experience:

  1. Locate the ID of the Account/Contact/Invoice/Tax/TrackingCategory referenced in the validation message.
  2. On the Sync Results Page, make sure the 'linked' option is active in the filter at the top of the table.
  3. Use the search bar filter to enter the copied ID, and your record should appear with a corresponding validation message.
  4. Read the 'Detail message' provided. If additional guidance is needed, select the More info link.

By addressing the underlying issue detailed in the validation message and ensuring all records are correct and synced in both systems, you can resolve these errors and maintain an uninterrupted data flow.

Was this article helpful?