QlikView document with a table loaded with INFO prefix. Any Drop statement in the script after INFO LOAD not only removes the given table, but also drop the Info table.
Refer to Info-Load-Error.qvw
in the attachment below for a sample qvw document with this issue.
In this particular case, there is no established link between the INFO table and a logical table. This means that the info of the INFO table is never fully linked to the actual data (not recommended) and the INFO table is effectively an orphaned table. All orphaned tables will be dropped with a drop table statement without being explicitly listed in the drop table statement. This is an intentional cleanup process where orphaned tables are automatically purged from the data model (that they do not belong to anyway).
The INFO table must contain two columns only:
- The first one with the field values that will form the keys to the information and should be linked as a key field to a logical table
- The second one containing the information elements, that is, the file names of the pictures etc.
Only the first field (i.e. the key field) will be visible as a field name. Unless this key field is actually linked to a logical table, the info table will be an "orphaned" table.
Refer to InfoLoadKeyAsLogicalKeyNotOrphan.qvw in the attachment for a solution where the previously orphaned table has been linked to the data model and is now considered a valid logical table that will not be affected by the orphan table cleanup.