Making changes to fields/option set

(0) Share

Report

Posted on by SR11

Hello,

Our company recently bough Dynamics 365 for sales. I am currently supporting it but I am completely new to it. Asking a very basic question here - whats the best practice when making minor changes like updating options in an option set field. Would we create a new solution in sandbox, make this change and then import the solution in prod?

Categories:

Other

I have the same question (0)

All responses (5)

Answers (1)

LuHao 40,892 on at

Like (0)

Report

Hi partner,

Welcome to Dynamics 365 Community.

You only need to customize the default solution, no need to import the solution.

Please follow the steps below:

1. Log in to D365 as the system administrator and go to Dynamics 365 - Custom. Then go to Settings > Customizations > Customize the System.

2. Under Components, expand Entities, and then expand the entity you want. Select Fields. Double-click the field you want to edit. (Here is an example of the field of the Account entity.)

3. Click on the option and you can modify its Label. You could also add options, delete options, move options, or sort all options alphabetically.

4. Finally don't forget to save. In this way, the option set field is updated.

I recommend that you read the official documentation for Dynamics 365, and you could find instructions for using most of the features:

[View:https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/create-edit-fields:320:50" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" class="gallery_video_main" allowfullscreen>

In addition, you could also refer to this video:

Last but not least, if your problem is solved, please click "Yes" to mark the verified answer. This will help other users with the same theme, if they have the same problem, they can refer to this post directly.

Hope this helps.

Best Regards,

Lu Hao

Was this reply helpful? Yes No
SR11 54 on at

Like (0)

Report

Thanks for your answer. I have a follow up question- I see that you are suggesting making this change directly in production but isn't it best practice to make changes in dev/test and then push these to production?

Was this reply helpful? Yes No
Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report

Hi SR11,

The best practice is to create a minimal unmanaged solution in your development instance containing only the components you are changing. When you are happy with the changes, export the unmanaged solution from your development instance and deploy it to your UAT and production instances. I do not recommend making changes directly in production or in the default solution.

Was this reply helpful? Yes No
LuHao 40,892 on at

Like (1)

Report

Hi partner,

I agree with Adrian.

If you are applying changes to production instance, it is not recommended to directly customize the default solution for production instance.

The last answer I gave was to operate in the sandbox instance.

You could use Adrian's solution.

Hope this helps.

Best Regards,

Lu Hao

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (1)

Report

Hi,

You should create solution and add/create component inside it for any kind of changes in your dev environment , so that you can export as managed or unmanaged solutiin and import to your production. Make sure you create new publisher while creation of solution so that you can identify easily the solution component.

There is many things you need to understand while working with solution.

Go through below article for more understanding-

docs.microsoft.com/.../introduction-solutions

docs.microsoft.com/.../solutions-overview

In addition there is a critical decision while moving solution whether you export managed or unmanaged solution from dev to import in production. For me you should always use one base solution and change over thereby create patch for every minor delivery and while export you should use managed solution so that you could easily uninstalled.

You should also know about solution patch-

docs.microsoft.com/.../create-patches-simplify-solution-updates

goutamdascrm.wordpress.com/.../solution-patch-in-microsoft-dynamics-365

Was this reply helpful? Yes No