Skip to main content


Run form Objects Usage Setup from object designer


Trace only Reports – used when we want to monitor only reports usage. This kind of setup will have minimal performance influence to the system as it only iterates through codeunit 1 trigger OnFindPrinter, which is triggered when user runs a report. Object Usage Entry records will have exact time when reports were run.

Trace all Objects – used when we want to monitor all objects usage. This kind of setup can have medium performance influence as it is based on NAV Code Coverage functionality, which will be started automatically in codeunit 1 trigger OnLoginStart. Code Coverage starts to slow down user NAV session after some running time (when virtual code coverage tables become very large), so it is a reason why automatic Code Coverage cleaning is implemented.

Clear Code Coverage after iteration – it determines count of iterations (call to codeunit 1 trigger CaptionClassTranslate) after which tool processes gathered Code Coverage lines, creates temporary object usage history records, clears all Code Coverage lines and resets counter to 0. Object Usage Entry records will have time entries when this processing was performed. Lowering this field value will influence more exact log time, lower memory usage by Code Coverage, but higher processor usage.

Trace for All Users – if checked then objects usage will be performed for all users. If not then system will log objects usage only for defined users in User setup.