Answered

Something went wrong error message when trying to view data from virtual table

(0) Share

Report

Posted on by ctedesco3307

938

trying to create a virtual connection to a view via SQL Server connection. I'm able to create it but then I get this error. Can anyone help? View is very simple just 4 columns

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Suggested answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@ctedesco3307,

Columns in your view can be null. I think a virtual table requires at least one column that can be the unique key and that can't be null.

Try modifying the view to add the ID field from the original table and see if it doesn't work then.

MS Learn

Get started with virtual tables (entities) (Microsoft Dataverse) - Power Apps | Microsoft Learn

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
ctedesco3307 938 on at

Like
a
(0)

Report
Copy link

Link copied!

@MS.Ragavendar Thank you for responding - there are no null values and I have VendorID as the primary key. Do I need to make a GUID as the PK? TY

Was this reply helpful? Yes No
Verified answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@ctedesco3307,

You mentioned VendorID as PrimaryKey from the screenshot the datatype might be double or nvarchar while dataverse requires a unique identifier of type uniqueidentifier (GUID) to act as the Primary Key.

Primary Column Requirement
Every Dataverse table must have a Primary Name column (typically a text field such as VendorName). Although you already have VendorName, the issue can occur if the mapping logic attempts to use VendorId as both the unique identifier and the primary name. This conflict can cause the mapping process to fail.

How to Fix the SQL View
Update your SQL view to explicitly include a GUID column. If your source table doesn’t already contain a GUID, you can generate a stable one by deriving it from the VendorId (for example, using a hash). This ensures the value remains consistent and prevents mapping errors.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No