Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
To start off, I'm rather new to PBI so I'm kinda building the airplane while in its in flight.
I am trying to set up a set of reports that refresh often (no fixed time need, but more often than every 30 minutes). My research has led me to Direct Query. My data lives in the cloud and it is PostgreSQL with a Personal Gateway and a "PRO" account.
To do ODBCPostgresDirect I apparently needed a custom data connector (??) which I got and installed from these links:
and
Connector extensibility in Power BI.
So I'm pretty sure I have a functioning ODBC driver (Unicode x64) and system DNS. I say that because I can load and refresh my data model on the PBI desktop app. I hit the wall when I try to use the reports on PBI Service.
When I do a manual refresh I get the little orange triangle with the error message:
Going into the settings I'm presented with:
After trying "Discover data sources" I get this response:
My Google-Fu has reached it's limits.
Thank You!
Solved! Go to Solution.
Thanks again for responding @GilbertQ ,
As it turns out, I had forgotten that I moved our gateway to a different machine from the one I'm working on currently. Once I logged this machine in to the gateway, everything worked fine.
P.
Hi @GilbertQ. Unfortunately none of those steps helped. When I use the native data source PBI won't connect (connection time out). If it helps, Ive only had success with ODBC connections (hence that 3rd party connector).
Hi @P_Crane31
I would use the native Power BI Data source as shown below
When you connect to the data it should then ask you if you would like to import it or DirectQuery. You select DirectQuery.
Then in your gateway you would need to configure the connection details with username and password to connect via the gateway through to your database.
Power BI data sources - Power BI | Microsoft Docs
Power Query PostgreSQL connector - Power Query | Microsoft Docs
Thanks again for responding @GilbertQ ,
As it turns out, I had forgotten that I moved our gateway to a different machine from the one I'm working on currently. Once I logged this machine in to the gateway, everything worked fine.
P.