nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DAuditTrail and LiveReport execution

Patrick_McManus

DAuditTrail logs an event when a user runs a LiveReport, but is the event logged when the user initiates the report, or when the report completes and the results are displayed? This could be significantly different for long-running reports.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

Ian_Whitfield

Long-running SQL statements won't be audited until the query is complete. The audit is written after the SQL statement has been executed and the data has been returned from the DB but before the web page has been built on the server to send the results back to the browser.

All comments

Ian_Whitfield

Patrick_McManus

Thanks, Ian. It would be really useful if two separate events were logged in DAuditNew - one when the LiveReport was initiated, and another when the results were returned from the database....

Ian_Whitfield

Fair enough. Feel free to log a feature request with support for the additional auditing. If you're licensed for Webreports you could probably do something like this as a workaround:

1) Log a before audit event using the AUDITACTION tag.
2) Run a SubWebreport that has the Livereport as its data source.

Regards
Ian