Can you make selector item non selectable in drop-down list?

[sliang20]

@SanfordWhiteman is the javascript you provided still usable? I've added it to my landing page template but the value still appears and it's not grayed out.

[Anonymous]

Thanks, Greg,

Leanne, the following article shows somewhat similar functionality implemented on a Marketo landing page.

https://www.linkedin.com/pulse/marketo-tip-automatically-cap-registrations-any-form-part-mba-6104062...

This allows to actually 'disable' the registration form? or display 'real time ' message on the registration page when the registration is full?

You might be able to use a version of this setup for your requirements.

Hope this helps...

Rajesh Talele

[Diederik_Marte4]

Thank you for the mention Greg! Both Rajesh and Sanford provided great solutions!

Though I would NOT disable registration. You still want the opportunity to capture someone's details. For this purpose I always automatically put registrants in the status "Pending Approval" and send them a temporary email stating an employee would get in contact to verify if there were still seats remaining. Then have a workflow that automatically sends an email (sorry,... or we hereby confirm...), based on the program status being manually updated to Registered or Rejected or WaitListed. This also provides some control on who will attend your event. Do make sure to write the Rejection email text well 😉

Alternatively you could auto-reject or auto-confirm (and have the correct email send) based on the amount of leads on the static list people are added to on confirm. You would need to call a webhook to a custom script to determine the amount of leads on the registrants list. That script would need the REST API to connect to Marketo and then use the ListController to determine how many leads were on the list: http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Static...

Or check for program membership of course.

[SanfordWhiteman]

Well, if you don't disable or mention sold-out events even though there are other available slots, you're just inviting oversold events. You can flag non-oversold events instead of disabling them, but not mentioning it makes little sense.

Would never use REST API calls on response to public traffic. Recipe for catastrophe!