Useage Context

Managing individual entity-specific sets of analytical paramenters can become an extremely consuming activity if the number of entities increases by more than a few tens or hundreds of items.
For example, there are man companies that have thousands, tens of thousands, or even more SKUs in their product portfolio, but the number of people responsible for managing these items is sitll limited.

In this context, in certain areas of interest, there are a number of properties that are in fact specific not to each entity, but rather to higher entities, but the logic of belonging to classifications having a separate logic of influencing individual specific parameters.

QQfallback™ Components

QQfallback™ consists of a Qlik™ script subroutine and a set of 2 configuration tables that contain, on the one hand, the hierarchical definition of the dimensions on which to fold, and on the other hand, the individual or group properties assigned to values of the entities in the hierarchy.

It is preferable to have a set of values in the second table for all parameters valid for the most general case (the whole company, which is the toop defined hierarchy), so that no entity of any level risks being left without a set of associated parameters. 

Cconfiguration and popular tables can be stored and managed in any spreadsheet tecnology (spreadsheet files, such as Microsoft Excel or Google Spreadsheet, CSV, XML or JSON files, or even tables in a database).

This algorithm can be used on its own, in the rapid population, by exceptions, of additional parameters on a large population, but which does not require a popular individual with individual and can be used to dfine relatively homogenous parameters on ….

Proceure call parameters define:




(… de luat din Documentarea procedurii)

Usage Examples

QQfallback™ was originally designed as part of a more complex project algorithm. QQinventory.healthcheck™ and QQinventory.prevention™, in which populating a set of parameters specific to hierarchically inhomogenoous families of items may be more efficient than populating hierarchically homogenous, or individual population at the finest level.

Here is an example from the context above:

We have several items, which have  a series of hierarchically defined classifications, as follows:


The company is the entity at the top of the hierarchy, which includes all the items, and the item is the finest entity in the hierarchy.

We want a larger set of parameters to be assigned to the items, but with as little hand information as possible.

The parameterization file defines a set of parameters for all the products in the company and then some exceptions, on different hierarchical levels, (including exceptions, exceptions, exceptions …).


When the QQfallback™ procedure is called, it reads the configuration tables and assigns the corresponding properties to all items in the nomenclature, obtaining a complete populace, based on definitions by exceptions:


For specific and specialized solutions from QQinfo, please visit this page: QQsolutions.

If you are interested in QQfallback™ product, please fill in the form here.

In order to be in touch with the latest news in the field, unique solutions explained, but also with our personal perspectives regarding the world of management, data and analytics, we recommend the QQblog !

For information about Qlik™, please visit this site: qlik.com.