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.
Qrew LegendI am not familiar with checking duplicates in excel. Have you tried making a summary report and QuickBase to group by that field? Then click the column twice to sort up the record count from highest to lowest. Maybe it's a situation where the user account has a leading or trailing space?
The approach in Excel was to download as a CSV file and then pivot on the key field. It didn't find any because the accounts were different.
When I followed your approach there were some duplicates (the accounts were different, but the name part of the accounts were the same). I removed one of each pair from the source table and repeated the exercise, but still no luck.
After some further selective pruning of the data I got the sync to work. I'm not sure what made the difference, but it worked. We have pipelines running overnight that may add some of the data back in, so it will be interesting to see if the sync keeps working.
