Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I created a solution and made the deploy to the production environment, but when doing so, I did it as a unmanaged solution. Now I need make some adjustments to this solution (Creating new fields, creating new business rules...), what is the best/recommended way to proceed? Keep in mind that I'll be making a lot of adjustments/adding new things. I'm planning on doing one deploy/version per week.
1) Delete the imported solution and when importing the v2.0 import it as a managed solution and keep updating it?
2) Keep the unmanaged solution and keep making the changes on it?
Thanks for your help!
It would be better to do the first option. It's best practice to do you changes (processes, customisations etc) and deploy them to production when you are ready.
Since you have already deployed the components to Prod as Unamanaged, there will be components on Prod in Unmanaged state. Deleting the solution will not change their state.
if you are to follow step 1, when you import the managed solution, you will get error saying the components already in Unmanaged state. To resolve this, you may end up deleting these components which also means you may lost data in if you delete any fields.
If this solution is internal to your company, not something you are selling to your customers, I would go for Option 2. Keeping solutions Unmanaged all the way through to Prod does give you a lot of flexibility besides, for internal or in-house solutions staying unmanaged it not a bad option.
Make changes in your dev environment and import these changes as unmanaged or managed solution in production.
Business Applications communities