Dropdown source patterns
Static choices
Simple Yes/No, status, or small option lists can become inline Power Apps choices.
SharePoint support list
Managed values should come from a supporting SharePoint list or library in the destination site.
Dependent choices
Filtered dropdowns need parent values, matching columns, and test rows that actually match.
Display value vs saved value
InfoPath often displays one column and saves another. For example, a dropdown may show a person name but save an email address. Power Apps needs both sides modeled clearly.
Validation checklist
- Open the dropdown in Preview mode, not just edit mode.
- Check that the support list has rows in the destination tenant.
- Confirm the dropdown Value property points to the display label, not the saved internal field.
- Save a record and verify the SharePoint value is what the process expects.
Common questions
Why does the dropdown arrow do nothing?
The control is usually evaluating to an empty table or data-source error. Check the Items formula and support-list connection.
Can a dropdown use a SharePoint list instead of SharePoint choices?
Yes. Many InfoPath dropdowns are better represented as support-list dropdowns when values are centrally managed.
Should I manually fix dropdowns after export?
Review every dropdown. The converter scaffolds common patterns, but production validation should confirm Items, DefaultSelectedItems, Update, and saved values.