Check out the latest Customer Service updates!Learn about the key capabilities and features of Dynamics 365 Customer Service and experience some of the new features.
Download overview guide | Watch Customer Service video
2020 release wave 1 Discover 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
Check records when an update is made to a field by CRM Administrators (Legal reasons).
Administrators made changes to the field 'fruit type' and option selected was "Mango" on the 30/1/17
but on the 1/2/2017 the fruit type Mango is now replaced with "mangoes"
want to be able to view these system changes as audit trail and records and which user(admin) made that change.
System limitation is D365 Online, no access to database.
There's no OOTB option to Audit Customisation changes. You could OOTB audit View and Security Role changes.
You could implement a set of plugins that runs on Publish and PublishAll messages which stores required details on a custom entity.
The bigger problem is who you give System Administrator access to. Even if you store the audit history in the custom entity, a System Administrator theoretically can delete the records since he/she has access to it. If you want to avoid that then you will have to store the audit details outside of CRM which CRM System Administrators don't have access to. Who ever has access to the external database can theoretically delete it from there as well.
Bottom line is, if you can't trust someone to do the right thing as a System Administrator, don't give them System Administrator access. It's best practice to minimise number of people who has System Administrator access, especially for Production instances.
You can create a custom entity for example -
A work flow can create records in the custom entity when the field values change.
There you can store all the necessary data, old value, new value, change by user etc.
Assuming only Admins can make changes to the field.
Business Applications communities