Skip to main content

Notifications

Customer Service forum

Version Control - Administrator change tracking as Audit trail

Posted on by 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:
  • Suggested answer
    Mihir@CRM Profile Picture
    Mihir@CRM 4,036 on at
    RE: Version Control - Administrator change tracking as Audit trail

    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.

  • Suggested answer
    Nadeeja Bomiriya Profile Picture
    Nadeeja Bomiriya 6,804 on at
    RE: Version Control - Administrator change tracking as Audit trail

    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.

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

Quick Links

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,818 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,147 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans