Announcements
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.
VendorID
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
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?
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 536
WarrenBelz 426 Most Valuable Professional
Haque 305
