Jun 21

Provide an option to set unique identifiers (keys)

At the moment, unique identifiers (keys in the JSON object containing form submissions) for every question are always auto-generated. Having the possibility of editing them to a custom value would allow for easier parsing and mapping on the webhook side. "data": { ... "fields": [ { "key": "question_nrza7l", "label": "Number of floors", "type": "INPUT_NUMBER", "value": 10 }, ... } In this example, instead of auto-generated "key": "question_nrza7l" we could set the key to "key": "number_of_floors"

Completed

Mar 7, 2024

Hi all, we just introduced a new way to name question fields via the `::` block options menu (screenshot below) which I believe is a solution to this feature request too. It's a way to give a field an internal name, which is not visible to the respondent. The `key` property in the webhook payload is the internal unique ID of the question, so it will stay as it is. The `label` property is the question title, which would have been "What is your favorite sport to do after work?" before, but with the new way of naming fields, this can be just "sport". I believe this makes it easier to parse through the webhook payload by looking up `label = sport`. Hope this makes things easier for you. Looking forward to hear your thoughts and feedback.

Mar 8, 2024

Filip Minev so now we cannot retrieve the label of the question? a new field for this would've been nice, "label" indicates that the value is a user-readable text which doesn't look like is the case anymore

Mar 9, 2024

ManHat: Yes, if you set the name via the `::` menu then the `label` won't necessarily be what the respondent sees. The goal of the `label` was not to define what the respondent sees, but it's meant to describe the field, so you as the form creator and webhook consumer know what it refers to.

Nov 7, 2023

This is really needed. Grouping a single page response into one is also needed. Right now, dynamic keys with un-grouped data makes it really challenging to extract data for large multi-page forms

Oct 5, 2023

Yeah the random keys aren't great to work with... It's do-able but still, we don't have this issue on the Google Sheets integration because it takes the label directly. Let's do the same for keys please ? This issue is the same with the Zapier integration by the way. I found this is even more annoying there than with the webhook.

Aug 16, 2023

Also, we need ability to set custom identifiers not only on the question level, but also for question options (for questions that have options). Those are autogenerated too atm.

Aug 10, 2023

Is not just the simplicity, is the extensibility we can have with this dynamic setup for attributes. Definitely the scalability will win here in a product that implements this.

Aug 9, 2023

I'd like to translate form fields into Keys. To change the webbook structure. To fix this right now, I'm sending the webhook Through a different automation that's Translating the web hook into the new automation.. Which feels kind of weird...

Jul 21, 2023

Yes, we need to be able to define an ID or label for each question. Indeed, it's way too complicated to dynamically parse the answers of a new form, so we need to create a custom code to parse each new form.

Jan 5, 2024

Actually, I didn't see it before, but it's easy to change the name of the question so it's easier to parse (I use directly the name of the attribute for the DB):

Jun 26, 2023

I'd perhaps suggest using an additional field to avoid too many technical changes internally instead of the default key, this would surely be quicker to implement

Aug 16, 2023

Yoann Bonnassieux: yes, that could be a new field!

Sep 18, 2023

Yoann Bonnassieux: Yes, that would be perfect