Qlik Community

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Not applicable

Debug include file

Hi,

does anyone know how to view included files while debugging inside Qlik Sense?

I can step inside an included file, and

i can see each line as it is being executed.

however, it would be useful to be able

- to see the full include file

- to be able to set a breakpoint in the include file

thanks a lot for your guidance.

5 Replies

Re: Debug include file

Within qlikview there appeared a further tab on the top of the debugger-window but in sense I don't know it:

- Marcus

vlad_komarov
Valued Contributor III

Re: Debug include file

Marc,

You can "step into" the include file, but you cannot set a breakpoint before the execution.

You can set in on the "include" line and move in... Once the include file is open during the debug mode, you can set up a breakpoint there...

Please note that there is a bug in 2.2.4 that affects the include files debugging: if you change the include file externally and re-execute the script (without re-opening the app), the updated lines in the include file will be executed correctly, but the debugger window will not show your changes....

Support has confirmed it as a bug.

Regards,

VK

Not applicable

Re: Debug include file

Hi Vlad and Marcus, thanks a lot for your answers.

the issue that i am facing is in Qlik Sense only.

here is a screenshot to illustrate that:

- the top part that should show all the code and let me set breakpoints is blank

- I only see the 1 line of the include file that is being executed in the bottom

qlikSense_debug_include.JPG

vlad_komarov
Valued Contributor III

Re: Debug include file

Mark,

It might be some issues with your browser (just a guess) since it's not a normal behaviour. Here is a screenshot from my system:

Screen Shot 2016-07-14 at 8.56.13 AM.png

Not applicable

Re: Debug include file

Thanks Vlad,

unfortunately it doesn't appear to be a browser issue.

I get the same behaviour using

- Chrome Version 52.0.2743.116 m

- Firefox

- Internet Explorer 11