- 🇺🇸United States richgerdes New Jersey, USA
@Webbeh,
Do you know if this is supported by the base webform's composite functionality? When the module was built, I don't think it was. I don't believe we are doing anything to prevent the use of any fields within this module, and just rely of the webform modules list of available composite sub element options, so if the base module has support it should just work here too.
Let me know if you are able to add a entity to a composite in a form and not to one of the global composites provided by this module, and I can look more into it.
- 🇩🇪Germany J-Lee 🇩🇪🇪🇺
This was asked some time ago in #3214847: Allow entity references in custom composite elements → .
But I think it's a good idea to make e.g. nodes selectable for some kind of product selector or whatever. - 🇺🇸United States richgerdes New Jersey, USA
Hi @j-lee,
I definately agree that this is a good feature to support, but it relies on the functionality being supported by Webform, so we'll need to get the issue fixed there first then ensure that this module fully supports it. @jrockowitz worked on this in #3214847: Allow entity references in custom composite elements → . There is a PR there which partially implements this. If this feature is required, we should work on getting that pr finished.
I'm here with him at the Drupal NYC Contribution Day, and the general sentiment i that the feature opens a lot of questions and will include a lot of complexity for handling the saving, display, and rendering of the entity reference values, which introduces a lot of complexity and will call a lot of development. This can also be implemented via a custom composite class if its really needed.