Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
datanibbler
Champion
Champion

Limited LOAD for debugging - also for development?

Hi,

I have read in another book on QlikView about a trick I did not know about before - I guess I had already read it in the first book I read, which is about the best I've seen so far, but I had not used it before - that is, the option to limit the LOAD to a specified nr. of records in the debugger.

My question is: Can I also use this option for development? By default, I cannot, because whenever I have an IF_clause with several options, depending on the values in a specific field, there is a risk that I miss one or several values because they just don't appear in the first x records. Is there any way around that risk or can I modify that? I think maybe the DISTINCT option would help - that would give me only one instance of every combination of fields, thereby increasing the chance that I would get one instance of every possible value?

Thanks a lot!

Best regards,

Datanibbler

1 Solution

Accepted Solutions
jonathandienst
Partner - Champion III
Partner - Champion III

You can dynamically apply a limited load outside the debugger like this:

  • Define a variable, let's call it vDebugLL

Set vDebugLL = 'First 100';

  • Add this variable to each load statement:

Table1:

$(vDebugLL)

LOAD ...

  • And to achieve a full reload, just chnage the variable to

Set vDebugLL = '';


This does not solve the problem with missing values, I don't have any simple solution for that, but normally when using limited loads for debugging, the purpose is to ensure that the script runs successfully, that the data model is correct and all the field names exist (so you can write or update expressions using new or modified field names). You can periodically do a full reload to verify the associations and full data set.


Distinct LOAD takes longer to perform than a normal load, and in most datasets, that is more likely to increase the LOAD time. Limited loads are normally used to reduce the reload time for testing.


Logic will get you from a to b. Imagination will take you everywhere. - A Einstein

View solution in original post

1 Reply
jonathandienst
Partner - Champion III
Partner - Champion III

You can dynamically apply a limited load outside the debugger like this:

  • Define a variable, let's call it vDebugLL

Set vDebugLL = 'First 100';

  • Add this variable to each load statement:

Table1:

$(vDebugLL)

LOAD ...

  • And to achieve a full reload, just chnage the variable to

Set vDebugLL = '';


This does not solve the problem with missing values, I don't have any simple solution for that, but normally when using limited loads for debugging, the purpose is to ensure that the script runs successfully, that the data model is correct and all the field names exist (so you can write or update expressions using new or modified field names). You can periodically do a full reload to verify the associations and full data set.


Distinct LOAD takes longer to perform than a normal load, and in most datasets, that is more likely to increase the LOAD time. Limited loads are normally used to reduce the reload time for testing.


Logic will get you from a to b. Imagination will take you everywhere. - A Einstein