Hi there!

Right now ExternalEntities treats all fields added that aren't part of the BaseFields as fields that are required to be mapped to the External Entity being pulled in.

I was wondering if we could perhaps at an alter so a user can choose which fields should be still mapped as drupal fields

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

sylus created an issue. See original summary.

sylus’s picture

FileSize
1.51 KB

This is just to address an immediate concern of mine, but I will circle back in as week or so and implement a proper alter().

sylus’s picture

FileSize
1.53 KB
rp7’s picture

Status: Active » Closed (won't fix)

If I understand the issue/patch correctly, I believe this is fixed in the 2.x banch (see #2995140: External Entities 2.x).
Only the id & label properties are required for mapping now - the other fields are optional.