web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Cannot bind Multi sele...
Customer experience | Sales, Customer Insights,...
Answered

Cannot bind Multi select option fields in external page form capture

(0) ShareShare
ReportReport
Posted on by Michele Cristofani 45

Hi all,

I have an external landing page and I'm tying to set up the marketing form capture for lead generation.

I'm not able to bind any HTML input to a Dynamics multi select field.

I've tried with:

  • <select> with "multiple" attribute
  • multiple <input type="checkbox"> with same "name" attribute

For the select, it allows me to choose only from option set fields (single, not multiple). For checkboxes, only boolean fields are displayed.

Any help?

Bye!

I have the same question (0)
  • Verified answer
    cloflyMao Profile Picture
    cloflyMao 25,210 on at

    Hi Michele,

    Currently multi-option set field is not supported for native page form or embedded marketing form or captured external form.

    From this thread, the support for multi-option set field will be added in Feb, 2020.

    Actually I found this new field type after I have enabled 2020 wave 1 release early access for my instance.

    pastedimage1582179454018v1.png

    It means that we could use native page form or embedded marketing form to show multi-option set field.

    but I'm not sure whether captured external form is also supported with new feature.

    My suggestion is that you could enable 2020 wave 1 release early access for your environment, then use embedded marketing form to display multi-option set field and create custom css rules to overwrite default style.

    Regards,

    Clofly

  • Michele Cristofani Profile Picture
    Michele Cristofani 45 on at

    Thank you for the answer,

    For now i'm going with the capture, adding a text field in the lead entity to store the unsupported field values (with javascript) and then running a custom plugin to extract this values and store them in the proper lead fields.

    Bye!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 209 Super User 2026 Season 1

#2
CU11031447-0 Profile Picture

CU11031447-0 100

#3
NeerajPawar Profile Picture

NeerajPawar 71

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans