Select Page

A new knowledge base article has been published on our support portal.

Scenario Overview

Many businesses import data from outside sources and they often will require either validation or clean up of said data. The below example details how any data that is imported in CRM can be put under strict validation rules or undergo any clean up process that may be required. 

This example shows how to set up a Decision Table to perform validation checks on imported data. An Example of a typical data set is below:

This example will use the following business rules:

Rule 1: 

The Renew Date column must contain Data
Rule 2:

The Amount column must contain Data
Rule 3:

The Account Type column must contain Data
Rule 4:

This import update will be matched to the existing Account entity via the Reference Number 
Rule 5:

Duplicates of this update are not allowed
Rule 6:

Only matching Account types are allowed
Rule 7:

All validation failures will create a relevant error message in the field Status Message
on the Integration Account entity
Rule 8:

If all validation passes, update a field in the Account entity with the next working day after 
the renew date - this field will be called new_nextworkingdayfromimport

N52 Formula Overview

The Formula Manager solution works like this: 

  • A custom entity called External Integration is created with the following fields:  Amount, Reference Number, Status Message, Type Number, Renew Date
  • The data is imported into this entity
  • A North52 formula is set to trigger upon the creation of an External Integration record
  • This formula will perform the validation checks and update any relevant fields

View this article in full on our support portal