I have two servers. They are deployed with ansible scripts, with an identical schema, identical postgresql user.
The only difference is that one is an older VM and uses postgresql v10 (a docker container) and one has the postgresql v12 docker container.
The schema has a carefully constructed set of foreign key relationships to help with automatic detection of relationships.
On connection and import to Power BI desktop, the data stored on the v10 postgres works wonderfully well: all table relationships are detected. On the v12 database, no relationships are detected. This happens regardless of import or Direct Query.
The schema is managed by django's ORM, which means the foreign key column names have _id suffixed at the end, so the foreign key columns don't have the same name as the unique column in the parent table.
Example: on the order header, we have order_guid as the unique column. The foreign key is order_guid_id
This can not easily by changed. It shouldn't matter, because the foreign keys are defined. It seems that there is a bug with the postgresql driver in Power BI desktop. I can revert to postgresql v10, so it's not the end of the world.
This is version info for Power BI Desktop
Version: 2.90.782.0 64-bit (February 2021)
This is power bi desktop
