>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3571040. --> Reported by: [bluegeek9](https://www.drupal.org/user/1286304) Related to !25 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The <code>primary_entity_reference</code> field type does not support the <code>entity</code> key format that Drupal's core serialization system uses during recipe and default content import. Standard <code>entity_reference</code> fields work with this format; <code>primary_entity_reference</code> fields do not.</p> <p>When using Drupal Recipes or Default Content with <code>primary_entity_reference</code> fields, YAML like the following does not populate the field:</p> <pre><pre>emails:<br>&nbsp; - entity: '676cfc78-1cac-5a48-b729-fbba59d7c230'</pre></pre><p>No error is thrown, but the field remains empty after import. The same structure works for standard <code>entity_reference</code> fields (e.g. the <code>contacts</code> field on <code>crm_relationship</code>). This prevents recipes from importing content that uses <code>primary_entity_reference</code> for fields such as emails, telephones, or addresses.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Create a recipe that imports content entities with <code>primary_entity_reference</code> base fields (e.g. a contact entity with <code>emails</code>, <code>telephones</code>, <code>addresses</code> fields).</li> <li>In the content YAML, reference related entities using the <code>entity: 'uuid'</code> format, with <code>_meta.depends</code> declaring the referenced entity type so import order is correct.</li> <li>Apply the recipe (e.g. <code>drush recipe:apply path/to/recipe</code>).</li> <li>Observe: entities using standard <code>entity_reference</code> (e.g. relationships) have their reference fields populated; entities using <code>primary_entity_reference</code> have those fields empty.</li> </ol> <p><strong>Example YAML that fails to populate <code>primary_entity_reference</code> fields:</strong></p> <pre><pre>_meta:<br>&nbsp; version: 1.0<br>&nbsp; entity_type: crm_contact<br>&nbsp; uuid: '00af71f6-cff0-5716-a2b1-323288beab04'<br>&nbsp; bundle: person<br>&nbsp; depends:<br>&nbsp;&nbsp;&nbsp; c5a34440-9a73-5685-881e-f929fe15356f: crm_contact_method<br>&nbsp;&nbsp;&nbsp; c753a2f1-3c68-50db-b069-a4c5957c7f10: crm_contact_method<br>default:<br>&nbsp; name: [{ value: Lisa Simpson }]<br>&nbsp; emails:<br>&nbsp;&nbsp;&nbsp; - entity: 'c5a34440-9a73-5685-881e-f929fe15356f'<br>&nbsp; telephones:<br>&nbsp;&nbsp;&nbsp; - entity: 'c753a2f1-3c68-50db-b069-a4c5957c7f10'</pre></pre><p><strong>Expected:</strong> <code>emails</code> and <code>telephones</code> are populated with the referenced <code>crm_contact_method</code> entities.<br><br> <strong>Actual:</strong> Fields remain empty; no error is reported.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add a custom normalizer so that <code>primary_entity_reference</code> field items support the <code>entity</code> key during denormalization (YAML &rarr; PHP), matching the behavior of core's handling for <code>EntityReferenceItem</code>.</p> <ol> <li>Implement a normalizer class (e.g. <code>PrimaryEntityReferenceItemNormalizer</code>) that extends the appropriate base (e.g. <code>FieldItemNormalizer</code> or the normalizer used for entity reference items).</li> <li>In <code>denormalize()</code>, detect the <code>entity</code> key with a UUID value; load the entity by UUID (e.g. via <code>entity.repository</code> or <code>entity_type.manager</code> + storage <code>loadByProperties(['uuid' =&gt; $uuid])</code>); convert to the <code>target_id</code> format the field expects; then call the parent denormalizer.</li> <li>Register the normalizer in <code>primary_entity_reference.services.yml</code> with a priority higher than the default field item normalizers so it is used for <code>PrimaryEntityReferenceItem</code> (or the module's field item class).</li> </ol> <p>This is an API addition (new normalizer service) and is backward compatible: it only adds support for a format that currently has no effect.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Implement the normalizer and register it in <code>services.yml</code>.</li> <li>Add kernel tests for denormalization of the <code>entity</code> key (UUID &rarr; <code>target_id</code>).</li> <li>Add an integration test that applies a recipe containing content with <code>primary_entity_reference</code> fields and asserts the fields are populated.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>New normalizer service for <code>PrimaryEntityReferenceItem</code> (or the module's field item class), used during content/recipe import. No breaking changes.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p> > Related issue: [Issue #3569755](https://www.drupal.org/node/3569755)