So, we know that there is a "Cube View Audit / Cube View - Updated" report. It doesn't show actual changes, but it's a start. Executing it in Design mode, we find it has a Data Adapter powering it:
The adapter definition tells us it's using a Dashboard DataSet rule:
Digging through that rule, we find it's actually using a Dashboard Extender rule:
Which itself is querying from table AuditCubeViewItem:
When we look at that table in our System/Database page, we see it has a bunch of fields stating when the change happened and who did it, but also "XmlData"
That's the state of the CV after it was saved at that time.
In order to show the actual changes, you will need to query that table, take the xml, and compare it between audit items. It's not trivial and will require some coding. There might be a Marketplace solution out there that could help, maybe have a look - I can't keep on top of all of them 😅
So, we know that there is a "Cube View Audit / Cube View - Updated" report. It doesn't show actual changes, but it's a start. Executing it in Design mode, we find it has a Data Adapter powering it:
The adapter definition tells us it's using a Dashboard DataSet rule:
Digging through that rule, we find it's actually using a Dashboard Extender rule:
Which itself is querying from table AuditCubeViewItem:
When we look at that table in our System/Database page, we see it has a bunch of fields stating when the change happened and who did it, but also "XmlData"
That's the state of the CV after it was saved at that time.
In order to show the actual changes, you will need to query that table, take the xml, and compare it between audit items. It's not trivial and will require some coding. There might be a Marketplace solution out there that could help, maybe have a look - I can't keep on top of all of them 😅
