Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Coming from #2090541: Avoid storing numeric target_id's for default values in field instance CMI files.
Entity ref values are manipulated and stored as local numeric ids for content entities.
The issue above overrides the handling of "default values" field settings so that, for entity_ref & taxo fields, the configured default values get stored in CMI using UUIDs rather than numeric IDs (and thus can be deployed).
This has raised the question of whether entity_ref fields could/should store UUIDs natively - whether instead or in addition to local IDs.
Discuss :-)
Comments
Comment #1
amateescu CreditAttribution: amateescu commentedOne obvious thing to point out is that storing UUIDs in addition to local IDs will create a disconnect between the configurable ER field and core's field, which cannot have more than one property.
Comment #4
jibranMoving to right component