Skip to main content
Version: V3.8

Understanding Unused Fields

One of the important uses for QSDA Pro is identifying unused fields in an app data model. You can then drop these fields from the model, saving server resources and typically improving performance.

QSDA only reviews field usage in the front end of the app. It does not consider usage in the load script.

While the QSDA field usage analysis attempts to be comprehensive, it may occasionally report a required field as unused. Always review the Drop Fields list before pasting it into your script.

The following conditions can cause QSDA Pro to miss field usage:

  • Section Access reduction fields.
  • Fieldnames or Expressions stored as field values in another "Dim" field, where the Dim field dynamically populates Dimensions or Expressions at runtime. QSDA does not examine field values.

To keep fields like these from being reported as unused, list them in the Collector option Field Names always in use. Matching fields are treated as used and are never marked unused or included in the Drop Fields list. Enter one entry per line: an exact field name, a field name pattern with * wildcards such as Sales*, or table: followed by a table name to include all fields in that table. Matching ignores case.