Blendr (a company that is qlik Documentation
The Blendr paperwork includes introduction videos, assistance articles, habits and API documents.
Design patterns to delete documents
See additionally the style habits when it comes to Blendr CDP, where we describe simple tips to delete documents while using the CDP.
Deleting documents should really be managed with care. You’ll want to e.g. make certain you try not to delete documents which were produced away from range of this integration. This does not always mean that contact with the same email address should be deleted in the destination CRM because this contact might have been created outside the scope of the current integration for example: when a contact is deleted in a source CRM with the email address «[email protected.
As a guideline, just delete documents in a location platform, that has been produced by the exact same integration. Always use a difficult match based on id to delete an archive (so-called «external id»), rather than a «fuzzy» match such as for example a message target or VAT quantity for the business.
- Include a sign in the below combinations to stop the Blend if the wide range of documents to delete is unexpectedly high ( ag e.g. count > 10). That is to make certain that no documents are deleted if for many explanation the foundation block «list documents» doesn’t get back any outcomes ( e.g. short-term problem with all the API associated with the supply platform).
- Set the «list» block’s error control to «Stop in error» to make certain that no documents are deleted by accident.
- Our advice will be exceedingly careful whenever blends that are implementing delete documents.
Utilize the «On delete» webhook occasion through the source platform, to delete documents when you look at the destination:
Note: verify to keep the id from the destination when you look at the supply platform (in a customized) industry or the other way around, to enable you to delete the precise record in the location, centered on its id.
A record in the Data Store for each creation of a new record in the destination) if this is not possible, use the Blendr data store to keep track of external ids ( insert. Example:
In the event that supply platform doesn’t provide «on delete» webhook occasions, you shall need to implement a «compare» Blend that compares all documents through the supply with all documents from the location. Documents through the location which are lacking through the source, could be deleted into the location. Example:
Our company is let’s assume that the id associated with supply is kept into the location as an «external id» in a customized industry, and also this industry can be used into the compare:
Note: this pattern is just legitimate once the location platform is really a «servant» associated with supply platform (master). Quite simply, we assume that no documents are manufactured by anybody or just about any process simply because they could be deleted predicated on this pattern.
An answer would be to filter record associated with location on e.g. a customized field that holds the outside id from the origin. Into the «Compare list» block, the asian dating login filtered list will be utilized to compare the foundation and location. Should this be maybe maybe maybe not possible, make use of the Data Store (see below).
If it’s not feasible to keep the id associated with supply when you look at the location (external id), the information Store can help keep an eye on documents which were developed into the location (see above). In this situation, the compare is performed involving the supply platform plus the information shop:
Keep in mind that the item can also be deleted through the information shop when it’s deleted within the location.