improvement(tables): throw on ambiguous upsert instead of guessing the conflict column

Author: TheodoreSpeaks

apps/sim/blocks/blocks/table.ts

@@ -283,7 +283,7 @@ Return ONLY the data JSON:`,
       id: 'conflictColumn',
       title: 'Conflict Column',
       type: 'short-input',
-      placeholder: 'Unique column to match on (defaults to the first unique column)',
+      placeholder: 'Unique column to match on (required if the table has multiple unique columns)',
       dependsOn: ['tableId'],
       condition: { field: 'operation', value: 'upsert_row' },
     },
@@ -646,7 +646,8 @@ Return ONLY the sort JSON:`,
     offset: { type: 'number', description: 'Query result offset' },
     conflictColumn: {
       type: 'string',
-      description: 'Unique column to match on for upsert (defaults to the first unique column)',
+      description:
+        'Unique column to match on for upsert (required if the table has multiple unique columns)',
     },
   },
 

apps/sim/lib/table/rows/service.ts

@@ -492,9 +492,12 @@ export async function upsertRow(
       )
     }
     targetColumnKey = getColumnId(col)
-  } else {
-    // No conflict target specified — default to the first unique column.
+  } else if (uniqueColumns.length === 1) {
     targetColumnKey = getColumnId(uniqueColumns[0])
+  } else {
+    throw new Error(
+      `Table has multiple unique columns (${uniqueColumns.map((c) => c.name).join(', ')}). Specify a conflict column to indicate which one to match on.`
+    )
   }
 
   // Validate row data