My Power App opens the wrong record when users edit from a gallery
A business Power Apps maker has a gallery, dropdown, or lookup that should open one request for editing, but the form shows, updates, or even overwrites a different record because the selected item, Item formula, LookUp, and form mode are not controlled together.
Context
The problem in plain English
If you're unfamiliar with this industry, start here.
Power Apps forms save against the record supplied to the form or Patch call. The user seeing a selected row is not enough; the formula must pass the correct record identity.
Key Terms
Industry jargon explained
Click any term to see its definition.
The Reality
A day in their life
Business professional asked to build internal Power Apps
I start the day by adding an edit screen to the request tracker. The gallery looks good, the search box works, and when I click a row the form opens. That feels like real progress because the app is finally more than a data-entry screen.
Then I notice the form is not always showing the row I clicked. Sometimes it stays on the first item. Sometimes a dropdown changes visually but the metadata does not follow. I try LookUp, Gallery.Selected, and a variable, and each version seems to work for one test record.
The scary moment is when a new form updates an existing item because I used an old record to prefill defaults. It is not a dramatic crash. It is worse: the app does something believable but wrong.
What I want is a boring proof before every edit. Show me the ID, show me where the selected record comes from, keep create and edit paths separate, and do not let anyone save until the app knows exactly which row it is touching.
The People
Who experiences this problem
Business professional asked to build internal Power Apps
25-50 • Beginner to early intermediate
Skills
Gallery filtering
Basic forms
SharePoint list IDs
Simple LookUp and variables
Frustrations
- The form shows the first record instead of the selected one
- LookUp returns a record but not the record they expected
- New and edit paths blur together
Goals
- Open the exact selected record
- Separate copy/default behavior from edit behavior
- Prevent wrong-row updates
Team user
Selects and edits business records and expects the app not to touch another person's item.
Also affected by this problem. Often shares the same frustrations or creates additional pressure.
Top Objections
- It works when I test with one record
- I can see the selected row on screen
- I thought FormMode.New meant it would create
How They Talk
Use These Words
gallerySelectedLookUpFilterItem propertyFormMode.NewFormMode.EditSharePoint ID
Avoid
record identity abstractionrelational modelling
Root Cause
Finding where this problem actually starts
We traced backward through five layers of "why" until we hit the source. Here's what's really driving this.
1
Why does the wrong record open or update?
The form Item or Patch base record is not tied reliably to the user's current selection.
2
Why is the current selection unreliable?
Selections can come from galleries, dropdowns, variables, or URL parameters, and each has different timing and shape.
3
Why does LookUp cause mistakes?
LookUp returns the first matching record, so vague or stale criteria can select a valid but wrong record.
4
Why do new forms overwrite records?
A New form can still have an Item formula pointing at an existing record if the maker is trying to copy defaults.
5
Why is it hard to catch?
Testing with one or two records hides wrong-record behavior until real users add similar records.
Root Cause
The root cause is weak record identity control. The app needs one clear source of truth for selected record, a separate create path for defaults, and tests that prove which ID will be updated.
The Numbers
How this stacks up
Key metrics that determine the opportunity value.
Overall Impact Score
82/100
Urgency
9/10
They need this fixed now
Build Difficulty
8/10
Complex, needs deep expertise
Market Size
6/10
Healthy demand exists
Competition Gap
8/10
Major gap in the market
"the form doesnt refresh to that item, it stays on the first record"
Maker using a lookup dropdown to choose which list item to edit. — Power Platform Community, 2026-04
More Evidence
What others are saying
"the item with ID = 5691 will get updated instead of creating a new item"
"I need help with updating existing records."
Older contextual practitioner example of create-versus-update confusion; current proof is carried by the 2026 community sources. — r/PowerApps, 2022-12-28
The Landscape
What solutions exist today?
Current market solutions and where there are opportunities.
Leader
M
Microsoft LookUp and Filter docs
Approach: Explain how Filter and LookUp find records.
Weakness: Does not teach a complete gallery-to-edit-screen identity pattern.
G
Generic gallery edit tutorials
Approach: Show Gallery.Selected connected to a form.
Weakness: Often skip edge cases like dropdown selection, deep links, copy-as-new, or stale variables.
The Fix
What a solution needs to succeed
The non-negotiables and nice-to-haves for any product or service tackling this problem.
The 3 Wishes
A record identity pattern that proves which row is being viewed, edited, copied, or created.
Must Have
Selected record source-of-truth rule
Gallery-to-form edit pattern
Copy-as-new safety pattern
Visible ID/debug label for testing
Wrong-record test cases
Nice to Have
URL parameter edit path
Dropdown-driven record picker
Out of Scope
Large-list delegation as the central topic
Complex relational Dataverse patterns
Role-based security
Success Metrics
Selected gallery row opens matching ID
New path creates instead of overwriting
Edit path updates intended ID
Copy/default path is clearly separated
Learning Pathway
Safe Record Selection in Power Apps
Know exactly which row your app is editing before the user saves.
Showing 1 of 1 recommendation
Course
◆◆◆◆◆Excellent Fit
Prove the selected row before the user saves
5 lessons120 minbeginner
You'll build: A gallery-to-edit-form pattern that proves the selected ID before save.
Solution Strategy
Which approach fits you?
A briefing can explain LookUp vs Filter, but a course is justified because the learner must implement the pattern and run wrong-record tests.
What we recommend
Create an atomic course with a gallery-to-form sample app.
The Future
What might make this problem obsolete
Technologies and trends that could disrupt this space. Factor these into your timing.
medium probability
Now to 12 months
Generated formulas still need wrong-record tests
Selection and identity checks become a core maker skill.
SaaS: Low risk
Course: Opportunity
Consulting: Opportunity
Content: Opportunity
For Creators
Content Ideas
Marketing hooks, SEO keywords, and buying triggers to help you create content around this problem.
Buying Triggers
Events that make people search for solutions
- A form opens the first record instead of selected row
- A new form updates an existing item
- A lookup dropdown does not refresh the edit form
Content Angles
Attention-grabbing hooks for your content
- Stop Power Apps editing the wrong row
- The ID label that catches gallery edit bugs
- Why LookUp finds a record but not always yours
- Copy-as-new without overwriting the source item
Search Keywords
What people type when looking for solutions
Power Apps edit form wrong recordPower Apps Gallery.Selected form itemPower Apps LookUp wrong recordPower Apps FormMode New updates existing item
The Evidence
Where this came from
Every claim in this report is backed by public sources. Verify anything.
1.2.3.4.5.
Using an Edit form to Update list item using a lookup dropdown
community.powerplatform.com
Power Apps form with Default Mode New and Item Lookup updates item
community.powerplatform.com
I need help with updating existing records
reddit.com
Filter, Search, and LookUp functions
learn.microsoft.com
EditForm, NewForm, SubmitForm, ResetForm, and ViewForm functions
learn.microsoft.com
5 sources referenced in this report
Collab365 Research • Collab365 Spaces
Have a question or correction?
No comments yet