Summary
To simplify the user interface and make managing relationships more intuitive, the "References" (relationship) object will merge with "Foreign Key." All existing properties will remain intact under the "Foreign Key" object with no impact to existing projects.
UI and object property updates
The "References" object will no longer appear in the user interface.
"References" will merge into "Foreign Key (FK)" objects:
"References" properties are now under the FK object combined with FK object properties.
The updated FK object inherits the related "Reference" display name.
Clicking on a relationship on a diagram or FK in Database Explorer opens the same property panel ("Foreign Key Properties").
Added support for Foreign Keys with no parent PK:
⚠️ A diagram error will be displayed for such scenarios.
Forward Engineering SQL and Get DDL via API
No changes
FK object naming convention for the existing projects
If the Relationship naming conventions rule is not enabled, a default Foreign Key NC rule will be used:
FK_$Table_$ParentTableName.If the Relationship naming conventions rule is enabled: the existing Relationship rule will be used for Foreign Key names.
Excel upload changes
Note that the Excel upload format has changed as a result of the merge so please be sure to download the latest project Excel before importing.
Please see the related article below for more details on XLSX import functionality.
See also