DQS uses a set of custom objects to store definitions, results, and scheduling data. All objects use the dataqualitysens namespace prefix.
Object Purpose Key Fields DQS_Definition__cScan configuration Name, Object API Name, Status, Description DQS_Definition_Detail__cField-level config Definition (lookup), Field API Name, Overrides
Object Purpose Relationship DQS_Dimension_Result__cPer-dimension scan result Definition (lookup) DQS_Field_Result__cPer-field result within a dimension Dimension Result (master-detail) DQS_Metric_Result__cDetailed metric per field Field Result (master-detail)
Object Purpose DQS_Batch_Schedule__cStores schedule configuration per definition
├── DQS_Definition_Detail__c (1:N)
├── DQS_Batch_Schedule__c (1:1)
└── DQS_Dimension_Result__c (1:N per scan)
└── DQS_Field_Result__c (1:N, master-detail)
└── DQS_Metric_Result__c (1:N, master-detail)
CMTs drive the configuration of capabilities and their evaluation logic. They are package-controlled and not editable by subscribers (except where noted).
CMT Purpose Records DQS_Capability__mdtDefines available quality dimensions 7 (one per capability) DQS_Dimension__mdtDimension display configuration 7 DQS_Metric__mdtMetric definitions per capability Multiple per dimension DQS_Input_Configuration__mdtInput configurator settings Per-capability config fields DQS_Configuration__mdtGeneral app settings Retention, feature flags
Event Purpose Calculation_Complete__eFired when a scan finishes processing DQS_Processing_Error__eFired when an error occurs during batch processing
Parameter Purpose DQS_AppEnabledControls activation gate — whether the app is licensed and active
