Answered

Dataverse choice column cannot connect to global choice

(2) Share

Report

Posted on by CU05050852-0

Hi Everyone,

I am currently developing a Power Apps application that is connected to a dataverse table.

After going through Microsoft Learn documentations and Copilot, you can use a global choice for a choice column but only after you have created the table.

However, after creating the table, the global choice option became disabled as shown in the image. Tried asking copilot again and unfortunately you cannot convert a local choice column to a global choice column.

Does anyone have a solution because my table has 300+ columns and 2/3 of it is literally choice columns (I really do not want to recreate the table again if possible).

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (2)

Sort by

Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

In Dataverse, it is not possible to convert an existing local choice column into a global choice column after creation.

The supported approach is to create new columns that use global choices, migrate the existing data into those columns, update the app to use them, and then

optionally remove the old columns.

While this requires some effort, it avoids recreating the entire table and is the recommended and safe way to transition to global choices.

Was this reply helpful? Yes No
Verified answer

Power Platform Guy 220 on at

Like
a
(2)

Report
Copy link

Link copied!

@CU05050852-0,

No, Dataverse does NOT support converting an existing Local Choice column to a Global Choice column. Once the column is created, the Sync with global choice setting is permanently locked. This is by design in Dataverse.

Create and edit choice columns overview

There is an option to convert the Convert Local Option set to Global Option Set try that.

☑️Accept as Solution to help others 💙 A Like is appreciated ❓Tag @PowerPlatform Guy for any queries

Was this reply helpful? Yes No
CU05050852-0 28 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Power Platform Guy

I have gone through the links that you shared. Unfortunately, the company does not allow installation of XrmToolBox on the company device.

Since there are over 200+ choice columns, I was thinking of trying to recreate the table instead of replacing the columns but change all the choice columns to lookup columns.

Is it a feasible solution or just better to replace the local choice columns to global choice columns?

Was this reply helpful? Yes No
Suggested answer

Vish WR 3,748 on at

Like
a
(3)

Report
Copy link

Link copied!

@CU05050852-0

In Dataverse, you can’t convert an existing local choice column into a global choice after it has been created, which is why the option becomes disabled.

The usual way to handle this is to create new columns that use the global choice set, move or map your existing data into those new columns, and then update your Power Apps to use them instead. Once everything is working, you can remove the old columns if needed

It does take some effort, but it’s the safest supported approach and avoids having to rebuild the whole table.

Was this reply helpful? Yes No
Suggested answer

Power Platform Guy 220 on at

Like
a
(1)

Report
Copy link

Link copied!

@CU05050852-0, Its deadlock situation in your case if Xrm Toolbox is not allowed in your company then no other option is available to convert the existing columns as mentioned by @Vish WR.

☑️Accept as Solution to help others 💙 A Like is appreciated ❓Tag @PowerPlatform Guy for any queries

Was this reply helpful? Yes No
Verified answer

timl 37,214 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @CU05050852-0

In response to this specific point, I would suggest replacing the local choice columns with global choice columns.

Whilst a lookup can be more flexible (as you can modify the values shown more easily outside of the designer), loading a single record at runtime with 200+ lookups would be much slower as each column value would need to be looked up, rather than the value being included in the payload of the source record.

>>Since there are over 200+ choice columns, I was thinking of trying to recreate the table instead of replacing the columns but change all the choice columns to lookup columns.
>>Is it a feasible solution or just better to replace the local choice columns to global choice columns?

Was this reply helpful? Yes No