You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(plugin-grid): block legacy import fallback for relation columns (#2164)
When the data source can't reach the server /import route (old
client/server), ImportWizard silently fell back to per-row create,
storing raw cell text verbatim — for lookup/master_detail/user/
reference/tree columns that writes display text where a record ID
belongs (observed in production: relation fields holding plain text).
The legacy fallback now refuses to run when any mapped column targets
a relation-type field, surfacing a clear error (i18n: embedded
fallback + en + zh) instead of corrupting data. Mappings without
relation columns keep working as before.
Fixes#2163
Copy file name to clipboardExpand all lines: packages/i18n/src/locales/en.ts
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -237,6 +237,7 @@ const en = {
237
237
requiredMark: '*',
238
238
required: 'Required',
239
239
invalidType: 'Invalid {{type}}',
240
+
legacyReferenceBlocked: 'Import blocked: {{fields}} are relation fields that need the server import route to resolve names into record IDs, and this connection doesn\u2019t support it. Importing them as plain text would corrupt the data. Upgrade the backend/client, or unmap these columns and import them separately.',
'grid.import.legacyReferenceBlocked': 'Import blocked: {{fields}} are relation fields that need the server import route to resolve names into record IDs, and this connection doesn’t support it. Importing them as plain text would corrupt the data. Upgrade the backend/client, or unmap these columns and import them separately.',
152
153
};
153
154
154
155
/** Apply `{{var}}` interpolation to a translation template. */
0 commit comments