Microsoft Dynamics 365 | Integration, Dataverse...

Deleted Value from Global Choice Still Shows in Target Environment

(4) Share

Report

Posted on by nvrhughes

319

We removed a value from a custom Choice in our dev environment, exported as managed, imported as upgrade to our target environment but the deleted value still shows in target environment,

There are no unmanaged solution layers in target environment.

Is this expected? Do I need to manually delete the value in each environment?

Thanks!

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Ramesh Kumar 7,566 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes — this is expected behavior when you're working with Choices (Option Sets) in managed solutions in Dataverse / Power Platform / Dynamics 365.

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
SJ-11090959-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hey @Ramesh Kumar

Otherwise, what is the recommendation to delete option set values in a target environment via deployment?

We're facing the same problem and can't understand why this could be exptected beahviour. Even though the official documentation says that it is possible to delete option set values of a global option set via deployment: Customize choices (Microsoft Dataverse) - Power Apps | Microsoft Learn

Only the publisher of a managed solution can import changes that delete an option from a global option set.

Thanks!

Was this reply helpful? Yes No
Suggested answer

Riazux 19 on at

Like
a
(0)

Report
Copy link

Link copied!
The key part of the Microsoft documentation is:

"Only the publisher of a managed solution can import changes that delete an option from a global option set."

If your solution upgrade is using the same solution publisher that originally introduced the global Choice, the deleted option should be removed during the managed solution upgrade. If it isn't, verify:

The solution is being imported as a Stage for Upgrade followed by Apply Solution Upgrade (not just Update).

The Choice belongs to the same managed solution and hasn't been introduced by another managed solution.

The solution publisher (publisher ID) matches the one that originally created the Choice.

The option isn't being reintroduced by another managed solution layer.

If all of the above are true and the value still remains, that is not expected behavior according to the documented lifecycle and is worth raising with Microsoft Support, as it may be a platform issue.

Was this reply helpful? Yes No