Common secondary sources
SharePoint lists
Choice values, status lists, people/role tables, routing tables, and department lists.
User sources
Current user, manager, role, or profile patterns that may need Office 365 Users or Entra ID-based logic.
External systems
SQL, SOAP, REST, or line-of-business integrations that need a connector or Power Automate strategy.
Required Settings best practice
- Enter the destination SharePoint site once, then load lists and libraries.
- Confirm the primary list or library and every required supporting list.
- Use real list IDs where possible so Power Apps imports data sources more reliably.
- Seed lookup lists with sample rows before testing dropdowns and filters.
Testing checklist
Open every dropdown
A dropdown that does not open usually means the Items formula is empty or the supporting data source is not connected.
Test dependent filters
Confirm parent-child filters, role filters, and status filters with real sample data.
Validate saved values
Check that the displayed label and saved value are both correct in SharePoint.
Common questions
Why do dropdowns fail after import?
Usually because the support list is empty, unresolved, filtered to no rows, or not reconnected in Power Apps Studio.
Does Form Migrator create supporting lists?
It can identify required targets and produce guidance. In some testing flows, a separate provisioning script can create lists and sample data.
Should lookup values be stored as display names or IDs?
It depends on the form. The converter tries to preserve the original displayed label and submitted value separately when it can infer both.