using tokens to pass paragraph values from fields in to webform does not work in 6.2 beta.

jjose.quevedo → made their first commit to this issue’s fork.

Hi @jrockowitz,

I've been attempting to reproduce the issue you mentioned, but found an error in the process. It's possible that I didn't replicate the issue accurately. Here are the steps I followed:

1. Created a new paragraph.
2. Added an email field to the paragraph.
3. Created a webform.
4. Added several fields to the webform.
5. Created a custom content.
6. Included the previously created paragraph as a field within the content.
7. Added the webform as a field and tried to insert a token, as shown in your screenshot.

However, I received the following error message:

Default submission data (YAML) is using the following invalid tokens

I'm wondering if I missed any steps or if there's something additional I need to do in order to reproduce the issue accurately.
Any guidance or assistance you can provide would be greatly appreciated.

Thank you!

Default submission data (YAML) is using the following invalid tokens

It is probably being triggered because the exact paragraph type and fields need to be created to replicate the issue. We might not be able to replicate the issue.

@alphex You could try using git bisect to determine which commit broke this functionality for you. That would help track down the problem.

I am not able to replicate this issue using the below steps

• Import the attached webform
• Enable the webform_test_paragraphs.module via `drush en -y webform_test_paragraphs`
• Create a Webform Test Paragraphs node via /node/add/webform_test_paragraphs
• Add the attached webform as a 'Webform test inline' paragraph
• Use value: '[paragraph:id] | [paragraph:field_webform_test_value:value]' as the default data
• Confirm the default data's [paragraph] token are replaced.

Some thoughts to debug your current setup

• Try a more straightforward token like [paragraph:id]
• Maybe the entity reference chaining is not working as expected

The only commit between 6.1.x and 6.2.x that impacts the Webform field is 📌 Add lazy builder support to the Webform render element. Fixed .

The attached is "shoot-in-the-dark" patch that reverts 758963d272020a1260c6ac6d017510ca5ea11523

@alphex Please try the patch in #11 and let us know if it fixes the problem for you.

I can confirm, the patch at #11 works for 6.2.x-dev

Thank you!

Okay, let's see if we can replicate and fix the issue.

Is lazy building enabled on the Webform field?

Per a discussion with @jrockowitz, this is not a release-blocker.

At this point removing the lazy builder behavior is not an options. We need to replicate and fix the issue.