No label Affiliation

Problem : 

During the review of the entity creation DCR, the data steward rejects one of the affiliated profiles and approves the other profile. However, the entity is created with a <No label> affiliation. What could be the reason for this?

Cause : 

This behavior occurs as a result of the Affiliation relationship configured between two entities. Although the data steward rejected one of the entities, the system still creates the entity to establish the relationship. 

Solution : 

When you are in the process of creating affiliated profiles using the DCR system, it is important to take into account the option to reject the “affiliations.” By doing so, you can prevent the system from automatically generating new affiliation entities that are labeled as <no label>. This step helps maintain clarity and organization within your data by avoiding the creation of ambiguous or unlabeled affiliation entries, which could otherwise complicate profile management and data integrity.