Answered

Virtual Table from a View - Something went wrong error

(1) Share

Report

Posted on by ctedesco3307

875

Hello- Trying to create a virtual table from a view and I get this - The view has these data types. Can I create a virtual table from this? Thank you inadvance

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

Pstork1 69,475 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

All the 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. Check this paragraph on mapping in the Virtual table documentation. Get started with virtual tables (entities) (Microsoft Dataverse) - Power Apps | Microsoft Learn

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
Suggested answer

11manish 2,293 on at

Like (0)

Report
Copy link

Link copied!

Technically, yes, you can create a virtual table from that view, but there are a few adjustments you need to make to the SQL view first to satisfy the Dataverse Virtual Table Provider.

Based on your SQL schema, here are the likely culprits:

Missing GUID column:
Dataverse requires a unique identifier of type uniqueidentifier (GUID) to act as the Primary Key. Your VendorId is currently an nvarchar(58). Dataverse cannot use a string as the internal system ID for a row.

The Primary Column:
Every Dataverse table needs a "Primary Name" column (usually a string like VendorName). While you have VendorName, if the mapper is trying to use VendorId for both the ID and the Name, it may crash.

How to Fix the SQL View
You should update your dbo.vw_APVendors view to include a GUID. If your source table doesn't have one, you can "spoof" one using a hash of the VendorId so it remains consistent.

Was this reply helpful? Yes No
Suggested answer

Haque 3,202 on at

Like (0)

Report
Copy link

Link copied!
Hi @ctedesco3307

Yes, you can create a virtual table from this view, provided you configure the virtual table entity in Dataverse to map the columns properly and designate VendorId as the primary key.

The view you targeted, columns are:

VendorId (nvarchar(58), null)

VendorGroup (nvarchar(30), null)

VendorName (nvarchar(255), null)

Source (varchar(10), null)

These are all text types, which are compatible with Dataverse text fields. The key point is whether VendorId can serve as a unique identifier for the virtual table. If VendorId is unique and stable, you can map it as the primary key for the virtual table.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Haque 3,202 on at

Like (0)

Report
Copy link

Link copied!

Hi @ctedesco3307,

I was following on this, any resolution?

Was this reply helpful? Yes No