Creating a new relationship, the Alternate Key, instead of Primary Key, gets cascaded to child entity
When creating a new relationship from an entity with an Alternate Key (AK) defined, the AK attribute appears in the child entity, instead of the Primary Key (PK) attribute. Can the PK cascade, instead of the AK, without removing the AK from the parent entity?
1) In the model, double click on the line, representing the relationship, that connects the two entities. 2) In the 'Relationship Properties' window, in the 'General' tab, select the drop down for the 'Parent Key' field and select the value that will cascade the correct key. You can see the name of the key that will cascade in the field below the Parent Key dropdown. 3) Click OK to save the change and the model will cascade the correct key in the child entity.