Unanswered

Virtual Table Error - We weren't able to open your table. Try reloading or reopening.

(0) Share

Report

Posted on by hari27pn

Hi everyone,
I imported a table from external table in dataverse. Now the table columns has been created but I cant find any row values in it.

I'm getting this message:
"We weren't able to open your table. Try reloading or reopening."

Please help me with this.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

codevenkat 126 on at

Like (1)

Report

Hi @hari27pn ,
I feel there could be some issue with the data in that source. Can you validate the columns data with reference to this post https://learn.microsoft.com/en-us/power-apps/maker/data-platform/limits-tshoot-virtual-tables?tabs=sql
Please share your findings, if you could solve this issue . Please mark this as accepted solution

Was this reply helpful? Yes No
hari27pn 18 on at

Like (1)

Report

I believe it is because of the GUID issue. As all other points seems to match with my data.

Was this reply helpful? Yes No
vavarier 2 on at

Like (0)

Report

Hi,
I am having the same issue, but I'm quite sure all my fields have the right type. Was the GUID your solution, or did you somehow find something else ?

Was this reply helpful? Yes No
secbulldawg 2 on at

Like (0)

Report

Did you solve the issue? I have the same issue. "Something went wrong. We weren't able to open your table. Try reloading " I am connecting to the Azure SQL server. I created three test tables with primary key types: int, GUID (unique identifier), and text (varchar). The table has one additional varchar field and three rows of data connecting via Entra. All three create the table but display the same message: "Something..." I also attempted a virtual table using an online tutorial using SQL Server Authentication but got the same result. Any suggestions?

Was this reply helpful? Yes No
TM-12091743-0 2 on at

Like (0)

Report

I was experiencing this same issue earlier today,

The solution I found was the SQL Database Permissions.

Inside the SQL Database, the Login User did not have access permissions to the Schema.

I have since resolved the error.

Was this reply helpful? Yes No