Valuekeep IntegrationsGeneral
IntegrationsGeneral
General
Back | List of Articles

Pipeline Hashing Synchronization

Last changed in 27/12/2024

Valuekeep Integrator adopts a version control based on a hashing system. Each pipeline has a version control, that is, it has a hashing key that allows to identify if the information subset (hashset) has still not been integrated or if it  suffered any change in the data, requesting a new integration. This hashing technique is applicable to an information segment (hashset), that is, it allows to identify the attributes that make up the hashing key (by ignoring integration requests when the entity suffers changes in attributes that are not a part of the key composition).
This method allows to synchronize a pipeline's hash, that is, synchronize the hashing of records that have been synchronized successfully, by avoiding later synchronizations, if there are no changes on the hashing attributes.

Method

The method used for that is: POST /api/mytenant/myorganization/integration/pipelines/synchash
Example (Json) for the hashing synchronization of a pipeline.

1.
{


"BaseEntity": "BusinessCore.Brands",


"ValueSourceHash": "VALUEKEEP",

    "FieldSourceHash":
"User_SourceHash",


"FieldTargetHash": "User_TargetHash",


"FieldIsSync": "User_IsSync"    

}

 

Description of the attributes available on the request:

  • BaseEntity: identifies the base entity (main table);
  • ValueSourceHash: identifies the hash key value on the source system;
  • FieldSourceHash: identifies the SourceHash attribute, when ignored, the system assumes: User_SourceHash;
  • FieldTargetHash: identifies the TargetHash attribute, when ignored, the system assumes: User_TargetHash. This attribute will be used to preserve the synchronized value;
  • FieldSyncHash: identifies the IsSync attribute, when ignored, the system assumes: User_IsSync. This attribute will
    be used to control if the record is synchronized (the records are classified for synchronization when the attribute value FieldSourceHash is different from the attribute value FieldTargetHash).

When this method is executed successfully, it returns HttpStatusCode.OK.

Bookmark or share this article
Esta página foi útil?
Obrigado pelo seu voto.

login para deixar a sua opinião.

Obrigado pelo seu feedback. Iremos analisá-lo para continuarmos a melhorar!
Related Articles
Pipeline Hashing Calculation Pipeline Monitoring How to obtain consumption records via by OData? Glossary WebApi - Pipeline Hashing Synchronization