Unable to Load Entity Catalog When Creating Virtual Table

[Anonymous]

I am trying to create a virtual table that reads an from on-premise PostgreSQL database. I believe I've been performing the appropriate steps, as follows:

1. Established the connection via an on-premises gateway (I know this was successful since a list of my local tables were loaded on creation)

2. Created a new solution with a connection reference to the connection from step 1

3. Created an app registration in Azure AD

4. Created a new virtual entity data source using my connection reference, along with the client Id, client secret, and tenant Id from my app registration

5. Waited to make sure the System Jobs related to the creation of this source were successful

6. HERE is where I run into problems

 - I am trying to load the entity catalog for my connection reference, and running into the following error:

This seems to be a system error, but if there is anything I can do to navigate around it (or anything I'm doing wrong) any guidance would be appreciated!

[Steven2019]

I was also getting the same error when trying to connect to a PostgreSQL database. After some research I've discovered that In this public preview release, Microsoft has introduced the virtual connector provider that currently only supports creating virtual tables using the SQL Server connector hence connecting directly to a postgres database is not working.

IN order to workaround this issue I've followed the instruction on the following site https://www.cdata.com/kb/tech/postgresql-connect-powerapps.rst which has allowed me to integrate live PostgreSQL data into custom business Apps built in PowerApps and below are my results.

I hope this helps.

[NHelgren]

At this time the virtual connector provider only has support for SQL Server, SharePoint, and Excel. Other types will come in time but you will need to create a custom connection for this purpose today.

[rjobaan77]

I followed bewlow steps but alos get error

http://powerappsguide.com/blog/post/connect-sql-server-model-driven-portal-apps-through-virtual-tabl...

I am using a SQL server connection, which is created before within a canvas app.

I get error Something went wrong. We werent able to open your table.Try reloading and reopening.

When i select the EntityCatalog 

[NHelgren]

Hi @rjobaan77, Does your SQL table have a GUID or Integer as its primary key? That is required for Dataverse to recognize it.

[rjobaan77]

I have a column called _#UID#_ of type GUID..

[rjobaan77]

the strange thing is also when i create a SQL server connection directly i dont get the option to fill in sql server name and sql database as i am getting when adding connection witin canvas app. How come?

I dont even see in when clicking on my SQL connection to which server its pointing....

[NHelgren]

Could you provide me repro steps to how you are creating that connection?

[rjobaan77]

Below steps for creating connection: 

I went to my enviroment

Clicked dataverse/connection

click new

search sql server

click on sql server

Authentication type: AZURE AD Integrated

click create

picked my account

and there is my connection without using any server or database

The connection name has now the name of my account I can not adjust that, when i click edit and adjust name and click Save, i got message "fix connection", if i click that , i need to sign in again so i use my account and the name of the connection remains the same.

Within canvas app

I create new canvas app

add data

search sql

click on sql server

now my connection which i created above is shown, so i select that one

now i get screen to fill in SQL server name and SQL database name

So i fill in those names anmd click create

now i see the tables of that database..

So within canvas app i goes fine

So question is why is it going wrong within model app

[NHelgren]

Let me follow up on that.