Can anyone explain why sometimes the audit logs displays the correct "new value" and other times it doesn't as below.
As you can see the actual audit record when double clicking does have correct "new value".
*This post is locked for comments
Can anyone explain why sometimes the audit logs displays the correct "new value" and other times it doesn't as below.
As you can see the actual audit record when double clicking does have correct "new value".
*This post is locked for comments
Hi,
I've tested this a fair bit and get varied results same field. Sometimes it shows the new value and other times it doesn't. This is the same date field I've been testing. This does not appear to be related to any processes.
CRM doesn't actually store the 'new value' in the audit log. The previous value is stored, but the 'new value' is derived when you read the audit data, either from the next most recent change to that field in the audit log, or from the current value.
This can lead to inaccurate information if auditing has been disabled, then reenabled.
Another possibility is that CRM stores the audit data for datetime fields as text. There is the potential for this to be misleading if different users have different date formatting settings
Hello ,
How you are updating entity data and when exactly its coming? Do you have any plugin , workflow register in the entity or you have any client side logic which occurs additional update.
It's not expected behaviour. I believe this os definitely not happening for all entity. So try to check what additional customization done for this entity or fields.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,280 Super User 2024 Season 2
Martin Dráb 230,235 Most Valuable Professional
nmaenpaa 101,156