Default selected items for modern combo boxes
Learn how to use Power Apps Default selected items for modern combo boxes with practical Power Apps guidance, implementation steps, common mistakes, troubleshooting, and related BuilderVault patterns.
What this pattern solves
Power Apps Default selected items for modern combo boxes is a practical BuilderVault pattern for makers and developers who need a repeatable way to handle default selected items for modern combo boxes inside a real Microsoft business app. The goal is to move past trial-and-error and give the builder a clear structure they can adapt to their own screens, flows, lists, tables, or environments.
Use this page when you are deciding how the pattern should work, what supporting data or permissions are needed, and what should happen when the happy path fails. The notes below focus on implementation fit, common mistakes, troubleshooting, and internal links to adjacent patterns so the build stays consistent.
Search intent
Help a Power Platform builder understand when to use Power Apps Default selected items for modern combo boxes, how to implement it, and what mistakes to avoid before using it in a production business app.
Problem
Combo boxes appear blank in edit mode when DefaultSelectedItems does not match the Items record shape.
What the finished pattern should include
- A maker can explain the control, formula, validation, and save behavior before release.
- The app gives users clear feedback for successful saves, missing values, and failed updates.
- The pattern can be handed to another builder without relying on hidden assumptions.
Solution
DefaultSelectedItems =
If(
IsBlank(selectedRequest.AssignedTo),
Blank(),
[selectedRequest.AssignedTo]
)Implementation checklist
- Confirm the Power Apps scenario and the business user this pattern supports.
- Identify the data source, owner, security model, and exception path before building.
- Build the smallest reusable version first, then add optional branches or polish.
- Test with realistic data, permissions, edge cases, and handoff expectations.
- Link this pattern to its collection, topic hub, and related implementation patterns.
Step-by-step instructions
- Inspect the Items schema.
- Return a one-row table for single-select combo boxes.
- Use Blank() when there is no saved value.
- Keep the default shape aligned with the patched shape.
When to use
- Modern controls
- Edit screens
- People, choice, and lookup selectors
When not to use
- Classic dropdown controls with simple Default values
Common mistakes
- Returning a record instead of a table.
- Using email text as the default for a people picker object.
Troubleshooting
- If the combo box remains blank, compare the selected record fields to the Items fields.
FAQ
When should I use Power Apps Default selected items for modern combo boxes?
Use Power Apps Default selected items for modern combo boxes when the same Power Apps scenario is likely to appear in more than one app, flow, list, table, or environment and needs a repeatable implementation approach.
Does this pattern work with Power Apps, SharePoint?
Yes. This pattern is written for Power Apps, SharePoint scenarios, but you should still confirm connectors, licensing, permissions, delegation limits, and environment rules before using it in production.
What usually causes this Power Apps pattern to fail?
The most common failure points are unclear ownership, missing validation, weak exception handling, undocumented permissions, and testing only the happy path.
Is Power Apps Default selected items for modern combo boxes beginner friendly?
This pattern is rated Intermediate. Beginners can use the fit guidance and checklist first, while experienced builders can move directly into the formula, flow, schema, or governance details.
Related patterns
Patch a SharePoint people picker field from Power Apps
Save a selected person from a combo box into a SharePoint person column.
Patch a SharePoint lookup field
Save a lookup selection with the Id and Value shape SharePoint expects.