Power Platform Community Forum Thread Details

@Emilia06

You're encountering an issue where a virtual table created from a Dynamics GP SQL connection in Power Apps shows no errors during setup, but fails to load with the message:

"Something went wrong, we weren't able to open your table. Try reloading or reopening."

This is a common challenge when working with Dataverse virtual tables, especially when sourced from SQL Server. Based on Microsoft's documentation and community insights, here are the most likely causes and how to resolve them.

✅ Key Troubleshooting Areas

1. Missing Required Fields

Virtual tables require:

At least one string field to serve as the primary name column
At least one GUID or integer field to serve as the primary key

If your Dynamics GP table lacks either of these, the virtual table will fail silently or show loading errors .

2. Unsupported Data Types

Dataverse virtual tables do not support:

File or image columns
Calculated or rollup fields
Attachments
Columns exceeding 4,000 characters

If your SQL table includes any of these, the virtual table may fail to render .

3. Data Gateway Configuration

Ensure that:

The on-premises data gateway is installed and running
The gateway is registered in the same environment where you're creating the virtual table
The SQL connection uses Windows or SQL authentication, not integrated security

Misconfigured gateways are a common cause of virtual table failures.

4. Table Permissions

The SQL user used in the connection must have:

SELECT permissions on the table
Access to any views or joins used in the virtual table definition

Lack of permissions can cause the table to appear blank or inaccessible.

5. Record Limits

Virtual tables are limited to 1,000 records per query. If your table exceeds this, and no filters are applied, the query may fail.

🛠️ Recommended Fixes

Check the SQL Table Schema
- Confirm it has a GUID or integer primary key
- Add a string column if none exists to serve as the primary name
Use a SQL View Instead
- Create a view that selects only supported columns
- Avoid joins or calculated fields
- Use this view as the source for your virtual table
Recreate the Virtual Table
- Delete the existing virtual table
- Recreate it using the simplified view
- Use the Power Apps Maker Portal → Tables → Add Table → From external data
Enable Logging
- Use the Monitor tool in Power Apps to trace the error
- Check the Dataverse plugin trace logs if enabled