- Issue created by @scbritton
Changing this to a critical bug report as nobody has responded and this strikes me as a critical problem with this module. If the form submission is updated, it should update the associated entity, yet fails to do so.
- 🇺🇸United States rpearl
I am playing with this module to see if it would fit my needs and I came across this bug. Once thing I noticed is the options for syncing are very similar so I started doing some debugging. As long as I checked "Synchronize Webform submission with the created content in edition?", this would run through the process of syncing webform and node with the node field of "field_submission_id". Within the fields for managing the conversion, you just need to make sure you are mapping that field with the forms sid value. This allowed me to save new field data based on the saving of the previous form submission.
In the yml file for the Webform Content Creator I also made sure the config was saving correctly. So in the config there is a line for:
... sync_content: true ...As long as this was true it was working just fine for me.
I am definitely doing all that. The difference is I want to also sync in both directions: If the webform is edited, the entity is updated; and if the entity is edited, then the webform is updated.
That said, I can work with updating just the webform rather than the entity.
But it is critical that, if the webform is deleted, then the entity is also deleted.
However, I went looking for the configuration yml file you indicated. Which file are you referring to? I looked in a number of files, and the only one which had a section that said "sync content" was the schema file, but that doesn't specify any settings at all. So, where is this particular line you're talking about?