qlik learning

concatenate when table 1 as a row and table 2 has same row both rows wil come after concatenation. Concatenate does not eliminate the duplicates. The NoConcatenate prefix forces two loaded tables with identical field sets to be treated as two separate internal tables, when they would otherwise be automatically concatenated. Qlikview will Autoconcatenate if the columns in both the tables are same. To avoid this we need to Noconcatenate option.

Comments

Post a Comment

Popular posts from this blog

Section Access

Section access is similar to reduction, but is done by the QlikView Server when a user accesses the document. The choice between section access and static reduction is a question of performance and memory usage. When QlikView Publisher opens a section access protected QlikView file, the file is reduced based on the reduction values Table Columns The following table columns are available: ACCESS, a field that defines what access the corresponding user should have. The following options are available in the drop-down list: l ADMIN 2 USER OMIT, a field that should contain the field that should be omitted for this specific user. Wildcards may be used and the field may be empty. A facile way of doing this is to use a sub field.
Read more

Binary Load

Advantages: Really FAST You can hide script from users. You can load a whole model with only one line of code Section Access also transferred Cons: Lack of flexibility Can load only one model Binary load is used only for one application means you are able to read data from only one QVW application and on the above of the set scripts is a restriction. should be done at the begining It does not load the layout information or variables you can load variables into a table in the source document and then retrieve them from the table (using peek()) in the target document. You could use an include file to hold the variable definitions and then call the include file in both QVWS.
Read more