The end date is populated in both the object and crosswalk level. Is this expected? The entity has been inactivated but the relation is still active. Is this a consistency issue?

Question

We recently saw that the end date is being populated at both object level and crosswalk level.

mceclip0.png

 

Answer

  • When DeleteDate is set for the crosswalk the Relation End Date is set automatically. This is working as expected. The only other scenario where it does not end Date relation is when we have multiple crosswalks and any of the crosswalks do not have the DeleteDate set.
  • The entity has been inactivated but the relation is still active. This appears to be a consistency issue and we should execute the following two jobs and verify the results.


 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.