Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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
You can dynamically apply a limited load outside the debugger like this:
Set vDebugLL = 'First 100';
Table1:
$(vDebugLL)
LOAD ...
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.
You can dynamically apply a limited load outside the debugger like this:
Set vDebugLL = 'First 100';
Table1:
$(vDebugLL)
LOAD ...
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.