Unanswered

Virtual Table data types

(1) Share

Report

Posted on by Sanketha

I have a SQL database with a table named Vendor, where VendorID is the primary key. Another table, Product, includes VendorID as a foreign key referencing the Vendor table.

After connecting these tables as virtual tables in Dataverse, the VendorID column in the Product table is appearing as a whole number instead of a lookup. I would like this column to be configured as a proper lookup field referencing the Vendor virtual table.

How can I achieve this

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@CU13051106-0 Hi,

Virtual tables created using the virtual connector provider automatically creates all the columns that are represented in the external source table. This will also include columns on which relationships are defined. However, the relationship definition won't be automatically created. You'll have to define this relationship in Dataverse manually.

Please check this article.

Setting up a virtual table relationship

Was this reply helpful? Yes No
Sanketha 4 on at

Like (0)

Report

Hi, thank you for the response.

In my scenario, the primary key in SQL and the primary key in Dataverse are different. I want to synchronize both systems so that they use the same primary key for consistency.

Current Issue (with Example):

I have a Vendor table in SQL where VendorID is the primary key. However, when I connect this table as a virtual table in Dataverse, the primary key becomes the vendor name, and I’m unable to select VendorID as the primary key.

This causes a conflict, especially when using lookups, since the expected reference (VendorID) is not available. Is there any solution for the same?

Was this reply helpful? Yes No