Alex Em on Thu, 03 Apr 2014 15:05:24
Since we have updated our Dynamics CRM 2011 with Update Rollup 16 there is an issue with the audit history. The "New Value"s for old entry (before installing the update) aren't displayed anymore. Instead a little icon is displayed.
Does any one have this issue too or knows a solution to display the values again?
Thanks in advance
MABR on Thu, 03 Apr 2014 19:53:55
Hi, this usually means that the Auditing feature was disabled or someone removed the auditing data.
Alex Em on Fri, 04 Apr 2014 06:48:48
With this hint I've found more on this topic:
We have also found a (unsupported) way of fixing this issue: due to the fact that the "new value" is either the current value or the old value of a subsequent entry, the information about the new value is not lost at all. The system just checks
if the audit has been turned off at some point and displays the icon after that. To avoid this you can delete the information about the deactivation and reactivation of the auditing. You will find this entries in the AuditBase table. "Action" is
104. Delete the two newest entries for deactivation and reactivation and the system will display the values again. We are aware that this might not be correct in the point of view that audit information can only be valid if the audit was enabled the whole
time, but in our case we deactivated the audit by accident during the update rollup and activated it
The best way would be: Never ever deactivate auditing once it has been activated.
Swathy Sajan on Wed, 31 Aug 2016 05:59:59
Please let me know is there any way to achieve the same in online environment.
When I tried with custom work flow to delete the same, an error message was showing, entity 'audit' is not available for deleting.
Daniel at VNS.net on Mon, 07 Nov 2016 06:10:29
Alex would you mind sharing the SQL you used to find and remove these two rows from the AuditBase table? I'm having the same problem - inadvertently turned auditing off/on for just a few minutes on an entity and now many audit records can't be read. Thank you
Daniel at VNS.net on Thu, 22 Dec 2016 23:50:49
answering my own question. this is what you execute in SQL to undo this. this fixes it on every entity in the system:DELETE FROM auditbase
WHERE Action='102' To enable it on specific entities:
DELETE FROM auditbase
WHERE Action='102' And ObjectTypeCode= 'ObjectTypeCode';
where objecttypecode = the entity from the metadataschema/entitytable
for OOB entiies, you get type code here: https://msdn.microsoft.com/en-us/library/gg328086.aspx
for custom entities you go from entitytypetable. for example, to find any named like hot sheets:
Select objecttypecode, * from Entity where name like '%hot%'
then replace each type code below with the right one you want. here's an example of 3 of them:
DELETE FROM auditbase
WHERE Action='102' And ObjectTypeCode= '10009' or ObjectTypecode = '1' or ObjectTypecode = '4';
Pat B on Thu, 23 Feb 2017 22:12:13
Thank you all, especially Daniel, for this information. I just noticed that this happened in our production system (CRM 2011) for the first time after years of importing solutions.