The purpose of the Document CAL is to provide a mechanism by which licensees can license the use of a single document. To prevent the combination of many data models in a single document, there are restrictions in the documents that can be used with the Document CAL. However, the Named User CAL, the Session CAL, and the Usage CAL can be used to open any functional QlikView document. The Document CAL can only be used with documents that have a single contiguous data model and do not contain any chasm traps between tables.
Most common data models used in QlikView documents can be used for Document CALs. For instance, proper star schemas and snowflake schemas typically have the field with the highest cardinality in the fact table and the keys in dimensional tables have a lower cardinality. For snowflake schemas, the cardinality decreases further when moving away from the fact table. Documents containing such models typically fulfill the above demands and are well-suited for Document CALs.
Documents with multiple logical islands are normally not allowed. Multiple logical islands are only allowed, if the additional tables are unconnected and contain only few records or a single column.
In addition, the document may not contain any loosely coupled tables.
Finally, the cardinality (that is, the number of distinct values) of the key fields must decrease when moving away from the fact table.
What happens now if I have a MasterCalender app for example. As the Master calender contains data for the last years in daily rows, it has somehow a cardinality which is comparable with the cardinatlity of the fact table.