Test TotalDropdown on the published page and inspect an actual form submission. The visible list can be correct while the form field name or received values are still wrong.
No choices appear
Check whether Blog Post or Blog ID is the correct source. For Blog Post, confirm that a current post is loaded. For Blog ID, check the exact ID. Then verify List from and confirm that the selected field contains published data.
The wrong choices appear
Recheck the source mode, Blog ID, and selected field. If similar data exists in more than one blog, confirm that the intended source is the one configured.
The form submission is missing the value
Give TotalDropdown a unique Field Name and inspect the received form payload. For multiple selection, confirm that the form processor accepts all submitted values rather than only one.
Required validation is not behaving as expected
Enable Required, publish, and test an empty submission. Repeat after switching between dropdown, radio, multi-select, and checkbox presentations.
Accessibility checks
Use a visible, meaningful label.
Use a useful placeholder and No Choices message.
Test dropdowns, the multi-select search, radio buttons, and checkboxes with the keyboard.
Keep selected and unselected states distinguishable with more than a subtle color change.
Maintain strong text, background, and border contrast.
Do not use Custom Classes to remove focus indicators.
If the problem remains, email support@stackswork.com with the TotalDropdown version, source mode, Blog ID with private details removed if needed, selected field, control presentation, Field Name, and a public test URL.
Related: Choosing the Total CMS 1 data source and field and Building single- and multi-select form controls.