Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

change custom field to be a global option set

(0) ShareShare
ReportReport
Posted on by 50

We have two entities which have both an identical option set. These option sets are both manual but have the same values.

So we want to change these option sets to be global ones.

There is no data in these entities but the solution is already in production and this is a managed one. So I think it will be a problem to delete these fields and create it (with same name) again but to be a global option set.

Is it possible to achieve this and how?

thx in advance

©a-x-i

*This post is locked for comments

  • Suggested answer
    gdas Profile Picture
    gdas 50,089 Moderator on at
    RE: change custom field to be a global option set

    Hi Axi,

    I would suggest not to delete field first , create new global optionset with different name (you can use same display name) and then import solution to production.

    Now after you delete the fields from your unmanaged solution  follow below steps  -

    - Select the unmanaged solution- Click on clone solution provide new version number and save.

    - Export the solution as managed .

    - Try to import the solution , you will find while importing checkbox called "Stage for Upgrade" , checked it and then checked "Overwrite customization"

    - Once deployed the solution , apply stage for Upgrade in the same window of solution import .

    Hope this helps.

  • Suggested answer
    RE: change custom field to be a global option set

    Hy Axi,

    You have to make first new  drop-down list then you can select the existing option set.

    3808.haha.png

  • Suggested answer
    Daniel Wikell Profile Picture
    Daniel Wikell 2,360 on at
    RE: change custom field to be a global option set

    Importing a solution which contains fields with the same name but different data type won't be accepted.

    Do you control the managed solution? With that I mean, do you have access to the unmanaged version of the solution in say a dev environment? If so you should be able to follow the steps described here to delete the fields in production first: community.dynamics.com/.../how-to-delete-components-from-managed-solution-in-dynamics-crm-2016-without-using-holding-solution

    After that you should be able to add the fields with the new type since they are no longer in the production environment and thus can't cause a conflict.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,409 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans