Making this code enhancement would obviously require a major update script to update the webform_submitted_data in order to populate the `data` field with the safe_key values instead, but I could see how "custom reports" that others may have written against the webform_submitted_data table may make this enhancement an impossibility without making an entirely separate field on that table. So, when I have a Option List in my webform like: someoptionSome Option I see in my view 'someoption' instead of the Readable Option: Some Option. I would think that custom reporting would be a nightmare without access to the items key values (if those are needed in that custom reports' criteria or grouping). Creating a view for showing my submission from my webform is working perfectly but I get the 'safekey' results instead of the 'Some readable option'.
Why provide a key value at all? If that key value is no used in any way, the items should just be entered freely as one entry per line with no "safe_key" at all. I've only tried the below for the CSV export, but I see no reason for it not working for MS Excel ones as well. I assume you download them in either CSV or MS Excel file format. The idea that each item option must have the format of "safe_key|Some readable option", I would infer that the "safe_key" is what is used in the backend.įor example, an item that determines whether or not the item is an invoice may have the webform_components record to have a `extra` value that looks like this: a:8:Įssentially, 1 is Yes and 0 is No. 1 Answer Sorted by: 5 I solved the above issue by creating a new Webform Exporter plugin, extending the default 'Delimited text' in a custom module. When a submission is stored in the webform_submitted_data table, it is storing the text values for the `data` value in this table and it should really be storing the "safe_key".
0 kommentar(er)
