Updated: How to log report usage

re: Updated: How to log report usage

Torben Wind Meyhoff - MSFT — Tue, 28 May 2013 10:50:04 GMT

@Benjamin

We do not have any run always triggers for reports, but what you can do is to make the same logging code inside the Codeunit1::FindPrinter trigger. C/AL SaveAsX methods invoked from the server will not invoke the trigger.

re: Updated: How to log report usage

Benjamin Hochstetter — Thu, 16 May 2013 08:57:12 GMT

Thank you for the interesting post. Is it planned to implement the trigger also for RTC. We are planing to upgrade our NAV 2009 RTC Customers to NAV 2013.

re: Updated: How to log report usage

DTACCONI — Tue, 30 Apr 2013 17:12:04 GMT

PART III

3. And Commit the temp table records into the Report Log table in Codeunit 1 Function LoginEnd

LogInEnd()

IF LogInWorkDate <> 0D THEN

IF LogInWorkDate = LogInDate THEN

WORKDATE := TODAY

ELSE

WORKDATE := LogInWorkDate;

IF USERID <> '' THEN BEGIN

IF UserSetup.GET(USERID) THEN BEGIN

UserSetupFound := TRUE;

RegisterTime := UserSetup."Register Time";

END;

IF NOT UserSetupFound THEN

IF GetGLSetup THEN

RegisterTime := GLSetup."Register Time";

IF RegisterTime THEN BEGIN

LogOutDate := TODAY;

LogOutTime := TIME;

IF (LogOutDate > LogInDate) OR (LogOutDate = LogInDate) AND (LogOutTime > LogInTime) THEN

Minutes := ROUND((1440 * (LogOutDate - LogInDate)) + ((LogOutTime - LogInTime) / 60000),1);

IF Minutes = 0 THEN

Minutes := 1;

UserTimeRegister.INIT;

UserTimeRegister."User ID" := USERID;

UserTimeRegister.Date := LogInDate;

IF UserTimeRegister.FIND THEN BEGIN

UserTimeRegister.Minutes := UserTimeRegister.Minutes + Minutes;

UserTimeRegister.MODIFY;

END ELSE BEGIN

UserTimeRegister.Minutes := Minutes;

UserTimeRegister.INSERT;

END;

ReportLogManagement.CommitReportLogUsage; //ADD THIS LINE

Hope this helps more in deploy the content of this blog without any side issue.

re: Updated: How to log report usage

dtacconi — Tue, 30 Apr 2013 17:11:37 GMT

PART II

1. Create a brand new SINGLE INSTANCE codeunit (called e.g. “Report Log Management”) like the following

these are the GLOBALS

Name DataType Subtype Length

tempReportLog Record Report Log

ReportLog Record Report Log

counter Integer

entryNo Integer

these are the FUNCTIONS

WriteTempReportLogUsage(ReportId : Integer)

IF tempReportLog.FINDLAST THEN

counter := tempReportLog."No." + 1

ELSE

counter := 0;

tempReportLog."No." := counter;

tempReportLog."User ID" := USERID;

tempReportLog."Report ID" := ReportId;

tempReportLog."Date Time" := CURRENTDATETIME;

tempReportLog.INSERT;

CommitReportLogUsage()

tempReportLog.RESET;

IF tempReportLog.FINDSET THEN REPEAT

ReportLog."No." := 0;

ReportLog."User ID" := tempReportLog."User ID";

ReportLog."Report ID" := tempReportLog."Report ID";

ReportLog."Date Time" := tempReportLog."Date Time";

ReportLog.INSERT;

UNTIL tempReportLog.NEXT = 0;

2. Then you can change your code in Codeunit 1 to populate Temp Table runtime with the following (just refined without logging NAS activity, if any)

OnReportRun(ReportId : Integer)

IF GUIALLOWED THEN

ReportLogManagement.WriteTempReportLogUsage(ReportId);

re: Updated: How to log report usage

dtacconi — Tue, 30 Apr 2013 17:10:49 GMT

PART 1

Many thanks to Timo to show us a way to implement this @best (of course you do not have the buffered report for still-on-line users). But as wisely stated, this should give the big picture related to logged report.

I have to say that I have touched the RUNMODAL problem with my own fingers and I just would like to add here AS IS and simple Proof Of Concept a way to get rid of RUNMODAL together with gathering the appropriate info.

From this blog you just have to create / change the following (again thanks Timo to illustrate a good investigation path):

re: Updated: How to log report usage

Timo Lässer [MSDynamics.de] — Wed, 24 Apr 2013 10:14:32 GMT

I also got the RUNMODAL error and solved this with a SingleInstance Codeunit:

The OnReportRun in Codeunit 1 calls a function of my SI Codeunit with the ReportID as parameter which saves all needed informations in a temporary table (defined as global Var in the SI Codeunit).

In Codeunit 1 - LoginEnd, I call another function of my SI Codeunit, which writes the records of the temporary table to the database.

This way, I can run reports modal and doesn't need a commit.

Sure, the statistics are updated at the end of the user session and new entries will be lost if the client crashes in any way, but in total, you will get an overview of the report usage anyway.

If you need exact informations in real time, this workaround is nothing for you. ;-)

re: Updated: How to log report usage

Rolf Kaufmann — Mon, 12 Nov 2012 12:54:17 GMT

Hi Claus,

I have the same problems as others with this code.

Report.RUNMODAL causes a Transaction Error.

and I found out, that your Statement:

>>OnReportRun is called before the first trigger of the report.

is not correct. I stepped though the code with the debugger and fuction 120 in CU1 is executed AFTER the Report.OnInit Trigger.

re: Updated: How to log report usage

Jon K — Tue, 28 Feb 2012 22:00:47 GMT

In regards to the RUNMODAL issue and avoiding a commit, an easy work around I am using is to create a table of "exceptions" and put

if not get.exceptiontable(reportid) then begin

...

end;

around Claus' code in codeunit 1 and as users come up with the RUNMODAL error, populate the exceptions table with the Report IDs. Not a perfect solution but still gets you a list of reports users are using by merging the two tables.

re: Updated: How to log report usage

Thomas K. — Tue, 01 Nov 2011 09:07:44 GMT

Any new information/experience with this feature, performance-wise?

re: Updated: How to log report usage

Thaddeus R — Mon, 15 Aug 2011 19:45:48 GMT

I do see one potential problem with this Mike. If a report is being run as part of some larger process, then when you COMMIT after the insert you would also commit any writes up to that point from the surrounding larger process. I personally don't think this is worth the risk, since the larger enclosing process (or the report) could encounter an error and then you would be leaving partially committed data.