Audits are a great way to see what has happened on records, what they did and more importantly who did it.
But if you have automated processes running that are pumping data into Dynamics because a field or two has changed, you might end up with an Audit History looking something like this.
In this case, an update was triggered, but it wasn’t until the fourth update that there was an actual difference in the data being changed. Even then, when we sent the whole packet of data, we sent it all.
With only four feels you can already see this gets a little painful to follow.