Skip to main content
Question

"Attempting to add a non-unique value to a field marked "unique" error on a QB Connected Table

  • January 13, 2021
  • 0 replies
  • 333 views
My connected table has been erroring out on the hourly table refreshes due to the following error:

 The error was: Trying to add a non-unique value to a field marked unique - Your import data has duplicate values for the following unique fields Field name: "

I was able to verify that the field in question does not have any duplicate values in both the source and destination table. In addition, the destination table already has the records in question within the table, so if anything, the records should be updated but there shouldn't be an error on the refresh. 

Has anyone else dealt with a similar issue? Not certain of what next steps to try aside from reaching out to QB Support.

------------------------------
Niraj Shah
------------------------------
This topic has been closed for replies.

Forum|alt.badge.img+14
Is the same field unique in both the origin table and the synced table? Or is the unique field only in the synced table?

If only in the synced table, check to see if there are multiple blank entries that are trying to sync. A duplicate blank will register as non-unique.

------------------------------
Mike Tamoush
------------------------------
SeanBoatMoore
Forum|alt.badge.img+5
Did you ever find a resolution?  I'm running into the same issue

------------------------------
Sean Boat-Moore
Manager SMB Development
Project Management Office and Quality Control
NCR Corporation
sean.boat-moore@ncr.com | ncr.com
------------------------------
Sean Boat-Moore Manager SMB Development Project Management Office and Quality Control NCR Corporation sean.boat-moore@ncr.com | ncr.com
    Forum|alt.badge.img+7
    • JeremyAnson
    • Registered
    • June 11, 2024

    Same issue here. Does anyone know what might cause it?

    MarkShnierYou
    Forum|alt.badge.img+22

     Have you tried running a summary report on the source table to group on the field in question to make sure there's no duplicates?

    Mark Shnier. Your Quickbase Coach
    Forum|alt.badge.img+7
    • JeremyAnson
    • Registered
    • June 11, 2024

    Hi Mark, yes, I checked on the source table, which has 'user account' as a key field (not sure why we did that when we created the table). There were a few accounts showing multiple records, where someone has two accounts linked to separate email addresses (so not identified as duplicates when checked in Excel). I've removed the 'duplicates' but am still getting the same error. 

    Terms & ConditionsAccessibility statement