Better Together T-shirt Design Contest
We're starting a “Better Together” T-shirt design contest. The theme is "Powerful alone. Better together," and we want to see your best T-shirt designs that encompass all 5 products in the family: Microsoft Dynamics 365, Power BI, Power Apps, Power Automate, and Power Virtual Agents. | Read More about T-Shirt Design Contest
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I have recently introduced a formal process for managing CRM change where we follow best practice... Stuff gets made or changed in Dev, moved across to Test using a Solution and then into Production using the Solution. I have set up a 2 weekly release window so that works when ready can be moved into Production at a fairly quick pace.
I am coming across challenges where previous CRM administrators who are used to making changes as and when they please in Production are trying to class certain changes as benign and therefore should be able to skip this process and continue to make the change in Production.
The example, or situation I have at present, is where a workflow needs modifying to add in a new email recipient to the details. They want to make this change directly in Production. My first reaction is NO, this is why I have set these rules and we are sticking by them. I gave the example that where the workflow is de-activated if a condition is met that should have triggered it the then workflow will not have been able to run. To which I then get asked if it's possible to do things like this but outside of working hours so helps negate the risk around this. My gut instinct is still NO.
I have said I will give it some thought so why not better to throw it out to the community to see what others are doing.
I need to be confident in my decision either way and would appreciate your thoughts.
I think you should follow your Guts. You are right.
The changes should not be made in the production.
It should be tested in Dev first.
Business Applications communities