mibuso.com

Microsoft Business Solutions online community
It is currently Sat May 18, 2013 7:48 pm

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 8 posts ] 
Author Message
 Post subject: Report Logging in NAV 3.7
PostPosted: Wed Mar 14, 2012 10:45 pm 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
Hi,

I read about report logging in NAV 5.0 and 2009 and it is very good.

We are still running NAV 3.7, is there a way to do the same?
Please advise.

Thanks,
Couber


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 4:35 am 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
Hi to myself,

Is it true that codeunit 1 always involved when running a report?

Please help.


Thanks,
Couber


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 5:26 am 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
I am thinking about adding code in FindPrinter to log reports not using systemprinter.
Since most of the reports are not using system printer and I can do a one time scan to identify how many reports are using system printers. This should work.

** The goal here is to figure out whay report was needed for new ERP system.


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 8:17 am 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
Well, I asked the question and I kind of played one man show here.

This is the blog helped me out:

http://blogs.msdn.com/b/nav/archive/201 ... usage.aspx

Even with NAV 3.7, I can use the idea in this great blog and comments about using FinfPrinter and using COMMIT to create a report log, with the exception that use system printer = yes.
One thing I did different is to add a usage counter to count how many times a report was used, with ReportLog.SETRANGE("Report ID",ReportID); and ReportLog.Usage += 1;

Thanks


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 10:27 am 
Offline

Joined: Thu Sep 07, 2006 1:46 pm
Posts: 14
Location: Poland
Country: Poland (pl)
Yes you can add some code in CU1\FindPrinter trigger, but the problem is that in this particular place system cannot
insert a record to any table :( so there will be error if you put there:
Code: Select all
ReportLog.Insert;


I had the same problem :( but I managed to solve it by force NAV to write the report-excecutions in the external text file.
p.s.
we have Nav 4.03 sp3

_________________
http://www.rtv-forum.pl


Top
 Profile E-mail  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 3:43 pm 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
easy-navi wrote:
Yes you can add some code in CU1\FindPrinter trigger, but the problem is that in this particular place system cannot
insert a record to any table :( so there will be error if you put there:
Code: Select all
ReportLog.Insert;


I had the same problem :( but I managed to solve it by force NAV to write the report-excecutions in the external text file.
p.s.
we have Nav 4.03 sp3


Yes, I did run into a big error message box. But the error message suggested to use COMMIT after the INSERT, or MODIFY, to fix the error. It was also confirmed by Mike G. of his comment on the blog mentioned above.


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Thu Mar 15, 2012 10:08 pm 
Offline

Joined: Sat Jan 28, 2012 4:48 pm
Posts: 56
Country: Netherlands (nl)
Be careful with a COMMIT which may be in the midst of a whole process.

This problem can also be overcome by using a temptable, see http://dynamicsuser.net/blogs/mark_brummel/archive/2009/12/01/tip-20-save-report-usage.aspx for details


Top
 Profile  
 
 Post subject: Re: Report Logging in NAV 3.7
PostPosted: Fri Mar 16, 2012 7:08 pm 
Offline

Joined: Thu Aug 17, 2006 4:10 pm
Posts: 225
Location: NY
Country: United States (us)
BernardJ wrote:
Be careful with a COMMIT which may be in the midst of a whole process.

This problem can also be overcome by using a temptable, see http://dynamicsuser.net/blogs/mark_brummel/archive/2009/12/01/tip-20-save-report-usage.aspx for details


Thanks.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 8 posts ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 11 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum


Search for:
Jump to: