Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We normally move all of our changes through the solutions. But we have a requirement so that we want to create a new security role in the production directly with the name 'abc'. But we are not going to create the same security role in any of our lower environment.
Is it the right approach? Do you think that this gonna create any problem in the future for the solution deployment?
Amit Kumar Rath
It is always recommended to carry all your customizations including security roles via solution packages as you were already doing it. It is difficult to comment on what challenges you would have going forward. I wonder what is the challenge this time around for not following the best practices! Making direct modifications causing unmanaged customizations is never the right approach. Try to refrain from it as much as possible.
D365 Support Engineer
Business Applications communities