RE: Audit History showing changes but values are the same
Hi,
when CRM is receiving some data, audit functionality is not looking at whether there were changes - it's only looking at what attributes were there in the incoming records.
Usually, CRM takes care of this problem on the user interface side (most of the times, it will only include updated fields into the data it'll send to the server)
There are a few scenarios when you can get this kidn of screenshot, though:
- There is a plugin/workflow that's updating the record and that's not looking at whether the update is, actually, required. In those cases, that plugin/workflow can easily set exactly the same values, and you'll see that as an update in the audit history
- You can have a javascript on the client side that will instruct CRM to always send specific field data to the server (when you click "save")