Import should allow to select _id (internal uuid) as a matching field for "entity" reference fields

[sleidig]

_As a user importing data I want to use the id of related records in my imported csv file in a column defining an entity reference field. I may re-import related data after having exported data with those IDs already from Aam earlier, so these are available and the most reliable way to match.

Proposed Solutions & Alternatives
In this special context of the matching field dropdown, also show _id field (with an understandable, human-readable label?), although we otherwise always filter this as internal.

Additional context
The same option should probably be available in step two, selecting fields to update instead of create new records from the import.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Import with hard-coded prefilled field to link to another record #3465
• mapping entity fields during import with empty(?) cells #3463
• Import UI: allow creation of adress string used for lookup from multiple import table columns #3422
• Use indirect / related entities as filters in Entity List #3343
• improve matching algorithm for import of existing records #3443

🔗 Related PRs

#3444 - Fix entity reference logic for import [merged]

👤 Suggested Assignees

• sleidig
• MalteHD
• Abhinegi2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!