QSDA Pro’s Resource Flags mark many fields as “Unused” that are actually critical in the load script (join keys, temp fields, mapping tables, etc.). Dropping them would break the data model.
This makes the “Unused fields” list very noisy, and we can’t trust it without manually checking every flagged field.
Is this expected behavior? Any good workarounds you use?
QSDA can only analyze what fields are required in the front-end. It does not analyze what fields are required in the script logic.
The recommended way to drop the unused fields is with a DROP FIELDS statement at the end of the script. At that point, the script is effectively complete and you don’t need to analyze what is required in the script.
The QSDA Script Generator Tool (Tools > Script Generator) can generate a complete Drop Fields statement suitable for pasting in your script.
See this help entry for additional notes about unused field analysis.
In summary, if you drop the fields at the end of your script you should not have to worry about impact on your script. If you want to not load the fields at all, then you will have to do some manual analysis to determine when to exclude the field.
You can mix the drop fields / exclude from load techniques if there is some benefit to do so.
What version of QSDA are you using? Key fields should always be considered by QSDA as in-use. If not, please open a support case with Motio support at https://support.motio.com/ and supply the support files and an export of the collection with the ticket.