Microsoft Dynamics 365
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.
This would be very useful to use planning optimization who are using custom dimensions since many years
Very much needed,