topic Re: Controlling the QDF TRACE output in Archived Groups

Controlling the QDF TRACE output

Tue, 22 Jul 2025 17:59:49 GMT

Hallo,

when developing an QV App using QDF one will get a lot of output in the script status window while running the script in the QV Client App. Most off this output belongs to QDF and, because QDF often works like expected, this TRACE output is worth nothing (see screenshot, german mode).

So the idea is, that QDF should implement loglevels an app developer could set in order to fine tune the QDF TRACE output.

A good idea is to implement same levels as other logging frameworks like log4j or leg4net use. It should be possible to switch off any QDF tracing as well as use of different levels up to debug level.

It should be possible to change the level within the script, so that some load parts run in high, others in low logging/trace levels.

So in the above example for me only my custom coded TRACE 'OD:12.08.2015 12:08:37 (UTC): Script beendet' is usefull for me. Most of the other output is not interesting for me.

If you like this idea just vote for it.

Regards

Frank

(Update: I added my code here, because the comment editor of ideas in this web interface has got no advanced editor. It is just possible to add a picture or a video)

Re: Controlling the QDF TRACE output

Anonymous — Wed, 12 Aug 2015 23:15:39 GMT

Hi Frank,

Why not write a sub-routine to do this? The QDF is community driven so I would recommend writing the sub-routine and submitting it with the idea.

Re: Controlling the QDF TRACE output

Thu, 13 Aug 2015 05:48:20 GMT

Hallo Damian,

do you mean I should write and post the code of a sub-routine, that does the TRACE Output based on a given level? If so, this sub-routine has to be implemented into the QDF sourcecode at each line, where a TRACE statement is.

If you mean that, here comes a question: Who holds the sourcecode of QDF? Is it in a GIT or SVN repository? How to access it? Who does the code merging?

Re: Controlling the QDF TRACE output

Magnus_Berg — Thu, 13 Aug 2015 08:04:57 GMT

Hi Frank, the framework is basically only Qlik scripts, nothing is compiles except the Deploy Tool that is more like a delivery mechanism of these scripts. I'm doing the code merging and sending out updated packages. So if you have an idea just create/modify the function add comments and post it into the community. If it's a good idea, implementation is correct and it doesn't break anything it will go into next release. Most important is that we keep consistency so that members can upgrade without risk.

Hope that this helps.

Regards

Magnus

Re: Controlling the QDF TRACE output

Thu, 13 Aug 2015 08:56:10 GMT

Thanks Magnus,

your answer helps to understand how the development of QDF is community driven.

Re: Controlling the QDF TRACE output

Fri, 14 Aug 2015 10:00:02 GMT

Hallo Magnus,

I have know done the coding and an example implementation within an InitLink.qvs. The Solution contains three files that I did not want to post to the community. It's some kind of "beta" code not edited by anyone. Is there a way to post a zip archive to you directly?

Regards

Frank

Re: Controlling the QDF TRACE output

Magnus_Berg — Fri, 14 Aug 2015 12:01:43 GMT

Hi Frank, thx. Just attach the zip into this discussion, I will have a look at it.

Cheers

Magnus

Re: Controlling the QDF TRACE output

Fri, 14 Aug 2015 12:17:49 GMT

Hi Magnus,

I had to add it in the main post, because this is an "idea" post and not a normal post. Comment editor has no advanced mode 😞

So see the zip file above.

Regards

Frank

Re: Controlling the QDF TRACE output

Magnus_Berg — Fri, 14 Aug 2015 13:33:05 GMT

Great! thx

Re: Controlling the QDF TRACE output

Magnus_Berg — Fri, 14 Aug 2015 14:14:17 GMT

It looks good Frank, is there any way to hide output other than trace? Seems a bit tiny to have a function that only hide the trace messages as most output are other things like AUTOGENERATE.

Cheers
Magnus

Re: Controlling the QDF TRACE output

Mon, 17 Aug 2015 06:37:58 GMT

Hallo Magnus,

as a "newbe" in Qlik I don't exactly know what is output that comes from Qlik itself and what comes from the QDF. So in respect to my screenshot you are right. Most of the output comes from AUTOGENERATE.

There is much more output in the QDF that comes directly out of Qlik and not out of TRACE statement within the Framework.

I have not seen any statement or configuration at document level to control the output QV itself does. I also have not seen any solution to switch off this QV logging within the script and switch it in again later in the script.

So as Damian said (see above): "This is community driven". So if somebody knows a solution for switching of the build in QV logging at some parts of a running script, feel invited to post it here.

If my posted solution is worth nothing, might be someone wants to use it anyway or QDF team decides to put it in the 4.Sub folder just like "7.CalendarGen" as a might be useful function-kit.

Regards

Frank

Re: Controlling the QDF TRACE output

Magnus_Berg — Mon, 17 Aug 2015 06:47:42 GMT

Hi Frank, It will go into the framework so don't worry I was just thinking if we can enhance the function in some way? Btw good work! /Cheers

Re: Controlling the QDF TRACE output

cotiso_hanganu — Mon, 17 Aug 2015 09:47:12 GMT

I was wondering, Magnus, have your team looked really deep into the work Rob Wunderlich did with his QVC ? Because it seems to me that at least some of his solutions should have been adopted in QDF...

Including the QVC.logging system (that might be a pretty simple solution to this issue.)

Re: Controlling the QDF TRACE output

Mon, 17 Aug 2015 12:08:03 GMT

Hallo Cotiso,

thx for your advice. I have never seen QVC before. It's new to me. To me it seems that it's a good idea to merge this two standards (QDF and QVC) into a big new framework.

But we have to be careful in mixing up words. So you know, frameworks like log4net use the word "logging". QVC also uses this word but Qlik scripting uses "tracing". In QV the word "log" is used for an mathematic function we all know well since we have been at school.

(Ok, in .NET and c# it might be an mathematic fuction as well).

But I think we should use the word "trace".

And: QVC.Logging just knows three log level, the approach I posted uses five levels.

Regards

Frank