Global Search: Measurements scope doesn't filter the individual measurement table by hierarchy tree selections

Keywords:
Signals Data Factory, SDF, Global Search, Spotfire for Signals, hierarchy tree, Organizational Hierarchy, H1 H2 H3, search scope, Measurements scope, Compounds scope, Batches scope, Assay Endpoint Results, AER, individual measurement table, measurement type not filtered, Measurement Conditions

Introduction: This article explains why the individual measurement type table can download unfiltered in Global Search when the search scope is set to Measurements and you've made a selection in the hierarchy tree. In the same search, the Assay Endpoint Results (AER) table is filtered correctly. The article also covers the recommended ways to get filtered measurement data.

Confirmed Behavior:

Example:

A measurement type is published to Signals Data Factory with a hierarchy of Department > Project > Experiment Name. In Global Search, the user selects Department = Biology and Project = AB02 in the hierarchy tree and then downloads the results to Spotfire.

• The Assay Endpoint Results table contains only rows for Biology / AB02.
• With the scope set to Measurements, the individual measurement type table contains rows from all projects.
• With the scope set to Compounds or Batches, the individual measurement type table is filtered through the AER hits.
   

Compounds / Batches scope: Compound (or Batch) hits > Assay Endpoint Results hits > Measurement hits. Hierarchy conditions are applied at the AER level.

Measurements scope: Specific measurements are filtered only by Material conditions and their own Measurement Conditions. Hierarchy conditions aren't applied.

Process Steps:

1. Check the Hierarchy Configuration
   • In Signals Data Factory, open the measurement type and review its Global Search Organizational Hierarchy (H1, H2, H3).
   • Check whether each hierarchy level is mapped to an attribute of the measurement type, or to a constant string or expression.
2. Choose the Right Search Approach
   • Option A: Use Measurement Conditions (Measurements scope). If the value you want to filter on (for example, Project) is an attribute of the measurement type itself, add it as a Measurement Condition on that measurement type in Global Search. Don't rely on the hierarchy tree selection.
   • Option B: Use the Compounds or Batches scope. Set the search scope to Compounds or Batches, so the hierarchy selection is applied through the Assay Endpoint Results.
   • Option C: Filter in Spotfire. Use the table relationship between the Assay Endpoint Results table and the individual measurement table to filter the measurement rows after download.
   • Note: Options B and C may download more data than you need. Option A is usually the most efficient way to get filtered results at the measurement level.
3. Verify the Results
   • Run the search, download the results, and confirm that the individual measurement table contains only the rows you expect.
4. Contact Revvity Signals Support
   • If you still get unexpected results, contact Support. Include your search scope, hierarchy configuration and any filters you applied.

Key Findings:

• Hierarchy Attributes Belong to AER:
  • The H1, H2 and H3 hierarchy attributes are defined on the Assay Endpoint Results measurement, not on the individual measurement type.
• Scope Determines the Query Path:
  • Compounds and Batches scope queries go through the AER, so hierarchy selections apply. Measurements scope queries don't go through the AER, so hierarchy selections don't apply to the individual measurement table.
• Expected Behavior:
  • This behavior is by design. It isn't a regression or a configuration error.

Critical Note: With the Measurements scope, hierarchy tree selections filter only the Assay Endpoint Results table. To filter individual measurement rows, add Measurement Conditions on that measurement type's own attributes.