What

In the Configurable syncronisations there are a configuration called: "Enable synchronisation to calculate for data changes to reduce the amount of logging and speed up the synchronisation"

• This setting is to ensure best possible performance on the jobs. It will mark the content with a hash value and use this value to calculate if the content needs to be updated on the job run.
• If enabled the synchronisation will scan the incoming data for changes before trying to synchronise the data.
• Configuration changes and Pure upgrades will always trigger a full run of the synchronisation. This feature is not supported by all data providers (Only Database (views) and XML, XML upload).
• The setting is enabled as default and was introduced in 5.12.X
• You might see a hash value added to the content.
• A hash is a value that is generated from the Person syncronisation source data.
• When a new synchronisation runs Pure generates the hash again with the latest source data. If there are any changes made to the source data, then the hash will be different, and Pure will know that a change has been made.
  • A setting in the job configuration will use this hash value to ensure that Pure only updates content with changes in the source. This is to increase performance with the synchronisation.
  • If needed it can be disabled in the job configuration.
    • Go to Administrator > Jobs > Cron job scheduling and find the job.
    • Click on Edit configuration
    • Click on Synchronisation configurations
    • Toggle off: Enable synchronisation to calculate for data changes to reduce the amount of logging and speed up the synchronisation.
      
• If hashes are disabled Pure will run through each information in the xml and cross-reference it with each information entry on that Person, which can be a bit performance heavy.
• Because the hash value will be used to skip some content, you might experience that some content does not get updated.
  • If a field is not being synchronised even though the configurations of the job should allow the synchronisation and there hasn't been any manual changes to the field. Then testing the synchronisation with the setting toggled off might help.
  • If the raw data is not changed, but the data referenced data is changing. Then it might be preferred to run this job with this setting toggled off. An example would be a setup where the URL to a profile picture stays the same, but the picture itself can be changed locally.
• The configuration is available on these jobs:
  • Configurable Activity Synchronisation
  • Configurable Course Synchronisation
  • Configurable Dataset Synchronisation
  • Configurable Equipment Synchronisation
  • Configurable Ethical Review Synchronisation
  • Configurable Event Synchronisation
  • Configurable External Organisation Synchronisation
  • Configurable External Person Synchronisation
  • Configurable Impact Synchronisation
  • Configurable Journal Synchronisation
  • Configurable Organisation Synchronisation
  • Configurable Person Synchronisation
  • Configurable Prize Synchronisation
  • Configurable Publisher Synchronisation
  • Configurable Student Thesis Synchronisation
  • Configurable Supervisor Synchronisation

Note: When Pure is updated from one version to another we regenerate all hashes which means all persons will be synced again. This is why you will see some times that only the hash have changed.