Suggested by M Fonsell – Planned
We still would like to have the option to use custom fields not tied to contact (nor lead) related to form itself and often to the event. Please reconsider this!
This was originally here in the idea called: "Non-mapped form fields" and now we are getting more and more comments that we still need it despite your documentation of "no need". Please reconsider!
Status Details
| Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap. Sincerely, Petr Jantac, Microsoft |
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.
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!
I see the status on this is "planned" in 2024 Wave 1, but I don't see it on the release plan. Is there an updated date for this?
Based on the comments I see that this idea was scheduled for 2024 wave 1 first and now for wave 2, but I don't see it on the roadmap. Can we expect it in wave 2 2024, or probably not?