HELPFUL: If you create more than one hidden field in this manner, you may want to tack on some sort of identifier as I've done in the example above, since the hidden field name does NOT ride along with the value. The safe key name actually does not matter here. Im using Webform MySQL Views to display webform submissions in a table, which is great. Without specifying this, the field can't be located and a null will be returned! In the above example, 'country' is nested under 'address'. Select Options- Yes, No, Other, or ecommerce options (safe-keyReadable Option).
IMPORTANT: Pay attention to the tree hierarchy. 'safekeySome readable option' seems to output the readable option regardless of using emailvalues, valuekey or emailkey. In some cases, related files have been organized under additional. It doesn't seem like it should work, since I understand that the 'submitted_tree' values are emailed in the first place, but it successfully returns the safe_key as a hidden field in the email. This allows even easier management of the questions you want to display in your grid, by setting for example specific filters on your view. $form_values = 'JobFunctionID: '.$form_values 1 Sure enough there is a way, a very neat one, just found it out myself In the following example I use a View's result to get the list of nodes I will use as the questions in the webform grid.
In a specific example: $form_values = 'CountryID: '.$form_values
#SAFE KEY SOME READABLE OPTION DRUPAL WEBFORM CODE#
The only thing that finally worked for me and my select fields was the following surprisingly simple code in the Additional Processing section of the webform: $form_values = form_values
0 kommentar(er)
