web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer Service forum / Version Control - Admi...
Customer Service forum

Version Control - Administrator change tracking as Audit trail

(0) ShareShare
ReportReport
Posted on by Teddyable 155

Check records when an update is made to a field by CRM Administrators (Legal reasons).

For Example

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.

Thanks 

Categories:
Customer Service
I have the same question (0)
  • Suggested answer
    Nadeeja Bomiriya Profile Picture
    Nadeeja Bomiriya 6,804 on at

    Hi Teddy,

    There's no OOTB option to Audit Customisation changes.  You could OOTB audit View and Security Role changes.

    https://dynamicsofdynamicscrm.com/2014/12/01/tips-and-tricks-some-gems-to-learn-for-auditing-on-customization-changes-dynamics-crm-2011-20132015/

    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.

  • Suggested answer
    MihirShah Profile Picture
    MihirShah 4,038 on at

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

🚀 Season of Sharing Community Challenge Launch!
Ask A Community Pro
Introducing our New Video Series: Community Spotlight

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Customer Service

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans