Unanswered

Choices values not updating after deployment to different environment

(1) Share

Report

Posted on by Community Power Pla...

I am working with a solution based in Dataverse with several columns that use global choices.

The issue I have come up against is that in the development environment we have removed some of the individual options but when moving the solution to the Test environment the changes are not visible.

The action within the deployment pipeline exports and them imports the solution as a managed solution.

Has anyone experienced something similar and could offer a steer?

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Michael E. Gernaey 53,315 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Did you remember to publish all customizations before exporting. If not then thats why.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (0)

Report

So an update on how the issue was rectified, or at least how I got the result I needed.

The choices values were simply not being removed and therefore all it took was for me to go into the relevant choices outside of the solution in the environment and change it there. This didn't create a managed layer so as far as I am concerned the issue is resolved.

I think it was a fundamental understanding of what is done with the import process when it comes to choices. As they are values, essentially the same as data in a table, these aren't not part of that function.

Was this reply helpful? Yes No
Thami on at

Like (0)

Report

In my case publish all customizations did not resolve my issue. I then opened my solution selected my table that depended on my global choice >> Advanced >> + Add required object , then ran the pipeline deployment successfully.

Was this reply helpful? Yes No
hq2200 2 on at

Like (0)

Report

I just encountered this issue. Unfortunately it appears that in my case, in addition to the regular solution layer, there was also a solution layer for each individual option within the choice. I had to tediously go in and remove each unmanaged solution layer for all the choices.
Choice->advanced->see solution layers->properties->choices->solution layers

Was this reply helpful? Yes No