Property values are synced with the data set using what we call a "synckey" which in this cas is a key identifier for a material. In the case of PCID and FireDb, the "synckey" that we use is the CAS Number property on Chemicals/Constituents. During a sync, the data set(s) is searched for the particular CAS Number and if data exists for that key in the content database, we send that data to CISPro and CISPro then determines what data can be used. Property values are synchronized in three different ways:

1. On creation of a new Chemical/Constituent (with a valid CAS Number).

2. On change of the CAS Number value of an existing Chemical/Constituent.

3. Whenever the "ExtChemDataSync" schedule rule runs and finds that the last data synchronization is out of date for a particular data set. For example, say that the ExtChemDataSync rule ran and synchronized PCID data on 4/10/2022. On 4/11/2022, we acquired new data and uploaded it into the database. This means that the newest version of the PCID data has a date of 4/11/2022. On 4/12/2022 when the ExtChemDataSync rule runs again, it will determine that there is newer data and it will re-synchronize with the data set.

To determine the last time an entity synchronized with either data set, add the "PCID Sync Date" and "FireDb Sync Date" properties to the edit layout. These properties contain a date-time value that corresponds to the last time the data was synchronized with the data set.