I have a rule which triggers after an webform has been submitted (d7).
The fields on a new entity are meant to be filled with some of the fields of the submitted webform.
Everything is working correctly except that only ONE 'set data value' works - the first one. Any other 'set data value' actions are ignored.
I have re-ordered, and recreated the data values. It doesn't matter which one I put first, it is the one that works. Subsequent 'set data value' actions after the first one are ignored.
In the attached screenshot you can see I have attempted a 'Conditional' as well, this is still ignored.
Re-ordering only changes which one gets fired off first, the rest are still ignored. Fields with default value have their defaults removed and become empty!
I'm hoping there's something obvious I'm missing because the first one works exactly as required, it's just the other that are ignored, even on re-arranging the action orders. Any ideas?
| Comment | File | Size | Author |
|---|---|---|---|
| set data value.jpg | 137.82 KB | petarb |
Comments
Comment #2
petarb commentedComment #3
petarb commentedIssue resolved. Moderator please marke as closed.
Instead of the parameter of the webform submission [data:department-value], I used the UI to obtain [data:department:0]
I'm not completely sure what the '0' means (array position?), but this issue is resolved. The hints on the page could be enhanced, since the '[data:department-value]' entry I had keyed in matched the hints....
Curious though that the first action ALWAYS worked despite its contents.
Comment #4
tr commentedFor future reference, you can do that by yourself ...