Usage of PartialLoad in QlikView

Problem description: it is true that PartialLoad is a good thing. In the previous blog, we talked about its usage and specific effects. However, after discussing with our friends today, we found that there is not much space to use in the actual production environment. The main reason is: PartialLoad does not execute the Load statement without adding Add or Replace, but Pa

Problem description: it is true that Partial Load is a good thing. In the previous blog, we talked about how to use it and its specific effects. However, after discussing with our friends today, we found that there is not much space to use in the actual production environment. The main reason is: Partial Load does not execute the Load statement without adding Add or Replace, but Pa

Problem description:

It is true that Partial Load is a good thing. In the previous blog, we talked about how to use it and its specific effects. However, after discussing with our friends today, we found that there is not much space to use in the actual production environment.

The main reason is:

Partial Load does not execute the Load statement without adding or Replace, but Partial Load does execute other statements, such as determining or calculating the number of rows in a table. Therefore, because the Load statement associated with other statements is not executed, for example, LET vRow = RowNo (TableName), other conditions in Script are used to judge this vRow, but this condition is not met. Or some Concatenate statements require tables that are not loaded, the program reports an error.

So, is Partial Load meaningless? In fact, even if the current QlikView 11 version does not meet the expectations of Partial Load, we can still reduce the time for loading a lot of data during our development.

For example, after I Load all the data on a Dashboard, there are already 500 mb. It takes about 40 minutes to load all the data each time. After Load, I found that one of my scripts was wrong. Do I have to Load all the data again? If you know about Partial Load, you may suddenly realize that we can temporarily use Partial Load in the development stage to Load all data with Reload during production or other stable environments. Some friends may ask how to temporarily avoid executing commands that they do not want to execute? My method is to use IsPartialLoad at the beginning of all code to determine first:

If IsPartialLoad () Then

Your partial load script

Else

Other script

EndIf

Test the partial load statement here and Load the entire statement, which greatly saves development time.

Another purpose is: because our project's current solution is to write the measure in excel, so we do not need to re-load all the data to test the newly written measure. This greatly improves development efficiency.

To sum up, the words on the QlikView Community are: Partial Load is not do nothing. we expect that the Partial Load in later versions of QlikView will be able to obtain the table value that already exists in the memory when the table that references the common Load is encountered, instead of making some if the value is null, some commands report errors.

Therefore, at this stage, Partial Load is not particularly suitable for Incremental Load. I will introduce other Incremental Load methods later.

However, using Partial Load to test the script being developed in the development phase can save a lot of time.