Start a new topic
Answered

Cross parent-child entities validation

Suppose you have a company entity and a subentity for contacts of the company.

The company enitity has a validation that companies without contacts are not allowed. The contacts have their own validation, such as for instance that country is mandatory.

When importing data both company and contact entities are set as tasks of the integration job, company being before contacts in the list.

When a company is imported with a faulty contact, neither the company nor the contact should be imported. 

How can we achieve this? At the moment the company is imported without errors, probably because the contact exists in the source tables at the time the company entity is processed.

Both are basic entities. (The use case is to migrate data into the entities)


Best Answer
  • If your entities were fuzzy-matched: you could use a Post-Consolidation validation on the parent entity
  • As your entities are basic, you must duplicate the child validations on the parent entity.
1 Comment

Answer
  • If your entities were fuzzy-matched: you could use a Post-Consolidation validation on the parent entity
  • As your entities are basic, you must duplicate the child validations on the parent entity.
Login to post a comment