Skip to main content

Generic

The Generic load prefix allows for conversion of entity–attribute–value modeled data (EAV) into a traditional, normalized relational table structure. EAV modeling is alternatively referred to as "generic data modeling" or "open schema".

Example of EAV modeled data and an equivalent denormalized relational table

Diagram showing transformation of a table with three columns and five rows into a table with four columns and two rows. The initial table has an 'Attributes' column, within which each entry gets converted to its own column in the resulting table: 'Status', 'Colour', and 'Size'.

Example of EAV modeled data and an equivalent set of normalized relational tables

Diagram showing transformation of a table with three columns and five rows into three separate tables. The initial table has an 'Attributes' column, within which each entry ('Status', 'Colour', and 'Size') gets converted into its own table. The 'Product ID' field remains constant in all tables.

While it is technically possible to load and analyze EAV modeled data in Qlik, it is often easier to work with an equivalent traditional relational data structure.

Syntax:  

Generic( loadstatement | selectstatement )

  • For more information about using LOAD statements, see Load.
  • For more information about using SELECT statements, see Select.

These topics may help you work with this function:

Related topics
Topic Description
Crosstable The Crosstable load prefix transforms data that is horizontally-oriented into vertically-oriented data. From a purely functional perspective, it performs the opposite transformation to the Generic load prefix, although the prefixes typically serve entirely different use cases.
Generic databases EAV structured data models are further described here.

Example 1 – Transforming EAV structured data with the Generic load prefix

Example 2 – Analyzing EAV structured data without the Generic load prefix

Example 3 – Denormalizing the resulting output tables from a Generic load (advanced)