To create a new entity field every time you need a new form field, that in the end you will might only use once, its time and money consuming. (as not all users know how to create this fields and they will require developers to do it).
A proper Form Submissions entity from which we can extract data into Excel would be very handy as well.
Lets look at the real life situation: if I have an event once a moth where I collect data for the guest's food choices, soon I will have dynamics full of options fields with different food options (as menu will be different each time)
And this applies to a lot of businesses that collect data from dropdowns about new products or services that they often offer.
Please can this be considered. Thank you.
Comments
There is another entry that asks the same thing (see "Non-mapped Form Fields") and it is marked as Completed. However, creating unmapped form fields is clearly NOT possible (our installation is less than a year old). This requirement is a MUST for many businesses and organizations, and is offered by other providers (e.g. ClickDimensions). We put several forms online every month, and each form contains several one-time fields. It is too cumbersome to create these fields in Dataverse every time. Please consider this urgently. Thank you!
Category: Marketing Pages, Forms, and Surveys
Can the title of this be changed to unmapped Optionset and two option fields please? I agree with this 100%. The two most common fields types that you'd want to use to drive customer segmentation based on form submissions is limited to being tied to mapped fields.
There are several other scenarios in D365 apps where you can define an optionset using just a comma separated list of values.
Similarly with two options - the response could easily be used to branch in journeys but you need to create a field in the database first to gain value out of it.
Category: Marketing Pages, Forms, and Surveys
Administrator on 2/17/2023 3:34:33 PM