sgoley / DirectQuery-for-ODBC-in-PowerBI

Direct Query for PostgreSQL via ODBC with SSL
MIT License
14 stars 9 forks source link

PostgreSQL Bug - new mashup engine breaks directquery connector #10

Closed sgoley closed 4 years ago

sgoley commented 4 years ago

Tracking a new issue where Custom Connector works correctly with old reports (regardless of PowerBI application version) but not with newly created reports.

Reproduce steps:

let Source = ODBCPostgresDirect.Database("Retro SF PG"), account_salesforce_d8b832js2t307u = Source{[Item="account",Schema="salesforce",Catalog="d8b832js2t307u"]}[Data] in account_salesforce_d8b832js2t307u

CurtHagenlocher commented 4 years ago

What version of Power BI Desktop are you running? You can get this from the Diagnostics tab under File | Options and Settings | Options.

CurtHagenlocher commented 4 years ago

Well, apparently I fail again at reading comprehension -- sorry!

mekam14 commented 4 years ago

Do you know if you have enabled the "Enhanced dataset metadata" preview feature in Power BI Desktop? Custom connectors aren't supported with that feature yet (they will in the June 2020 release of PBI Desktop). If you have this enabled then PBI Desktop will try to upgrade your reports on open, but if it identifies that it has custom connectors then it will fallback to the old format, but new reports would already be in the new format. This would explain why your existing pbix files still work, but copying the same queries to a blank report does not. If you do have it enabled, then please try disabling the preview feature, restarting PBI Desktop, and trying again. As I said, the next release of PBI Desktop will have support for custom connectors.

sgoley commented 4 years ago

@mekam14 This is it! Thank you for the quick response - it looks like the enhanced dataset metadata preview feature was the culprit.

image

Looking forward to that release very much now!