Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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
Comment | File | Size | Author |
---|---|---|---|
#3 | allow_for-2887193-3.patch | 1.53 KB | sylus |
#2 | allow_for-2887193-2.patch | 1.51 KB | sylus |
Comments
Comment #2
sylus CreditAttribution: sylus commentedThis is just to address an immediate concern of mine, but I will circle back in as week or so and implement a proper alter().
Comment #3
sylus CreditAttribution: sylus commentedComment #4
rp7 CreditAttribution: rp7 for Government of Flanders commentedIf 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.