Foreign keys not visible in database explorer

[pmscorca]

Hi,

when I create a relationship between two tables I've noticed that the related foreign key isn't visible in the database explorer, while for the primary keys at least it is reported the "pk" acronym: this is it a limitation or a regular behaviour?

Thanks

[pmscorca · Accepted solution]

Hi, it isn't possible to create a diagram to view the table relationships.

However the experience for both primary and foreign keys is to improve, certainly, also by implementing a graphic object to mark them, f.e. by a specific icon.

Thanks

[V-yubandi-msft]

Hi @pmscorca ,

Could you let us know if your issue has been resolved or if you are still experiencing difficulties? Your feedback is valuable to the community and can help others facing similar problems.

[V-yubandi-msft]

Hi @pmscorca ,

May I know if your issue has been resolved? If you need any additional details or clarification from our side, please let us know.

Thanks.

[V-yubandi-msft]

Hi @pmscorca ,

We haven’t received a response yet. Please let us know if you need any additional details or clarification from our side.

Thank you.

[V-yubandi-msft]

Hi @pmscorca ,

Thank you for engaging with the Microsoft Fabric Community. This behavior is generally related to how the tool displays metadata. The database explorer typically highlights primary keys, while foreign keys are not always shown in the same way.

If the relationship was created at the model level, it may not create a physical FK constraint in the database, which is why it doesn’t appear in the explorer.

If needed, you can define the FK explicitly as a database constraint. Otherwise, the relationship should still function correctly even if it isn’t visible in the UI.

Thank You.

[pmscorca]

Hi, I've created an explicit relationship using foreign keys and I'd like to see it in the explorer as it occurs for primary keys.

Thanks

[V-yubandi-msft]

Hi @pmscorca ,

Thank you for confirming that the foreign key has been created. Even with an explicitly defined FK, it might not appear in the explorer in the same way as primary keys. This is due to how the explorer displays metadata primary keys are often more visible, while foreign keys may not be.

There isn’t dedicated documentation on this, but the FK should still exist and function properly in the database.

You can also check the constraints section or use a diagram/model view to see the relationships more clearly.

Hope this helps.

[pmscorca · Accepted solution]

Hi, it isn't possible to create a diagram to view the table relationships.

However the experience for both primary and foreign keys is to improve, certainly, also by implementing a graphic object to mark them, f.e. by a specific icon.

Thanks

[V-yubandi-msft · Accepted solution]

Thank you for providing the additional details and your feedback. I agree that including a visual indicator for foreign keys, similar to the PK label for primary keys, would make it easier to identify relationships in the explorer.

Currently, this appears to be the expected behavior of the UI, not an issue with your configuration. Your suggestion to add an icon or marker for foreign keys is a valuable idea for improving the user experience.