There seems to be a mismatch of data in Global Search vs Signals Data Factory, why would this happen?

Keywords: Signals Data Factory, Signals Inventa, Global Search, AER, mismatch

Details: 

Sometimes, when there have been changes made in Signals Data Factory Data or maps, and “Load All” has not been performed, you may see differences in the following:

• Global Search
• AER (Assay Endpoint Result) tables
• Measurement tables
• Parent-Child measurement tables

If you see some mismatch, you may consider performing a Load All in Signals Data Factory

Load All creates a brand new index and will reindex all data in the project (assay and entities) based on whichever maps are currently assigned – this includes both primary measurement maps and secondary endpoint (AER) maps. Any existing index is left in place during this operation (e.g.: you can still query and download your previously indexed data while you are Loading All).

Once Load All is performed and completed, then there will be no difference in the data.

If no changes have been made to any data or maps, then there will be no difference in the data after the Load All.

*Some operations that will force a load all include: changing an attribute name, changing the data type for an attribute, and modifying the map for a compound/batch dataset.