Updated Choice value not showing on PowerApps

(1) Share

Report

Posted on by CourtneyPowell

Hi,

I recently had to add a new value on a choice field on a Dataverse table. Now the field on my PowerApp will not populate. I have refreshed the data, removed and added back the field and also published the table. Is there something that i'm missing?

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Michael E. Gernaey 53,969 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @CourtneyPowell

Did you remember to Publish all Customizations?

Was this linked to a specific Table? did you make sure to save that table as well, as well as publish all customizations (at the Solution(s)) level, NOT at the specific solution.

Was this reply helpful? Yes No

Suggested answer

MS.Ragavendar

6,334 Super User 2026 Season 1 on at

Like (0)

Report

Copy link

Link copied!

@CourtneyPowell,

Step	What to check / do	Why it matters
1. Make sure the Choices record exists everywhere	In the maker portal, open Tables → <Your Table> → Columns → <Choice column> → Edit Choice. Confirm the new item is there and that the choice set is Global (not a local copy).	If you edited a local choice (scoped to one table) but the app is bound to a global choice with the same name, the app never sees the new value.
2. Publish all customizations	In the Dataverse environment: Settings → Solutions → Publish all customizations.	Even though you published the table, other cached entities (the solution layer, the global choice set) may still be unpublished.
3. Clear the Canvas‑app metadata cache	In Studio: File → App settings → Upcoming Features → Use non‑blocking loaded metadata → turn Off, save, then turn On again. OR add a temporary blank screen, then File → Save.	Saving forces a metadata refresh more aggressively than “Refresh” on the data source alone.
4. Remove the data source AND the control, then re‑add	Delete the data card or dropdown bound to the choice → remove the Dataverse connection → Save → close Studio → reopen → add the connection back → insert a new dropdown and set its Items to the choice column again.	Controls hold a copy of the choice table inside their schema. A simple refresh often doesn’t rewrite that schema.
5. Make sure you aren’t using a hard‑coded Items formula	Check the dropdown / combo box Items property. If you see something like `["Option A","Option B"]`, replace it with `Choices([@YourTable].YourChoiceColumn)`.	Hard‑coded arrays don’t auto‑update when the choice set changes.
6. Confirm the app’s Preview is on the same environment	In the editor → top right, verify the Environment switcher.	If you’re editing in, say, a Dev environment but testing in Test, you may have added the choice to Dev only.

These are the common troubleshooting options which i know so far.

🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.

❤️ Please consider giving it a Like, If the approach was useful in other ways.

Was this reply helpful? Yes No

AS-28020259-0 2 on at

Like (0)

Report
Copy link

Link copied!

I do see the same issue when I don't use global choices on Dataverse. For now, not able to find a workaround without recreating the choice column and setting a global choice.

Hopping that in the near future a new version of power app will solve this issue with Dataverse limitation.

Was this reply helpful? Yes No