Skip to main content
Version: V3.8

Collector Options

Open Settings > Project Config > Collector Options to configure site defaults for new collections. Field Names always in use also applies when analyses are reloaded. When UI authentication is active, the Project Manager role is required. Save changes before starting a collection. App-specific choices such as a bookmark are available when launching an analysis.

Content and calculation​

OptionEffect
Collect published content / Collect unpublished contentSelect which content to collect. Published covers base and community sheets and objects; unpublished covers private ones. Both are enabled by default; Qlik permissions still limit accessible content.
Collect Calc TimeCollect chart calculation timings. On by default. Disable it to shorten a collection when timings are unnecessary.
Calculation scopeChoose Base sheets, Community sheets, Private sheets, and/or Master Library visualizations for calculation timing. All are enabled by default. This limits timing work rather than all metadata collection.
Include Disabled PropertiesCollect properties that normally have no effect on the app. Off by default.
Apply Sheet ActionsExecute sheet actions before calculating objects and checking expressions. Off by default; enable only when actions are required to establish the app's state.
Qlik TimeoutMaximum seconds to wait for a Qlik engine operation, such as a chart calculation. The default is 90; the allowed range is 5 to 9999.

Field Names always in use​

Matching fields are considered in use and are not recommended as unused fields. The list is read from the current configuration each time an analysis runs, so changes also apply when a saved analysis is reloaded. Specify one entry per line; matching ignores case.

CustomerId
%*
*_Required
table:Calendar

* matches zero or more characters in a field name. table:Calendar retains every field belonging to the table named Calendar. Table names after table: are matched literally, without wildcard expansion.

Use these exclusions for required fields whose usage cannot be discovered from the front end, such as Section Access reduction fields. See Understanding Unused Fields.