Power Platform Community Forum Thread Details

I created a lookup column on a table to a column on a virtual table. I wanted to use the lookup column on the related tables form for the user to select a value(from the virtual table). It's showing as locked on the form, with some additional options in the properties. Are virtual lookup columns not allowed to be used in related tables forms? I saw this search restriction below in the doc, wasn't sure if it pertained to this or not. IS there any way to do this?

Thank you

Categories:

Microsoft Dataverse with Power Apps

I also walked through these steps -- everything is set up correctly. Still seeing a lock on the field in the form

Here’s how you can use a Dataverse Virtual Table as a lookup column on a related table’s form in Power Apps / Dataverse.

Key Points Before You Start

Virtual Tables in Dataverse are read-only representations of external data sources (SQL, SharePoint, API, etc.).

You can create lookup relationships between a virtual table and a standard/custom Dataverse table, but:
- The virtual table must have a primary key and name column defined.
- The lookup will be read-only because virtual tables are not writable.

The relationship must be created in Dataverse table designer (not directly in the form editor).

Step-by-Step Guide

1. Ensure Virtual Table is Configured Correctly

Go to Power Apps Maker Portal → Tables → select your virtual table.

Confirm:
- Primary Name Column is set (this is what will display in the lookup dropdown).
- Primary Key is mapped to a unique identifier from the external source.
- Data is visible in the table (test by opening the table in Data view).

2. Create the Lookup Relationship

In Maker Portal, open the related table (the one where you want the lookup column).

Go to Relationships → + Add relationship → Many-to-one (N:1).

In the Related table dropdown, select your Virtual Table.

Name the relationship (e.g., new_VirtualTableId).

Save the relationship.

3. Add the Lookup Column to the Form

Still in the related table, go to Columns.

Find the lookup column created by the relationship (it will have the name you set).

Open the Main Form for the related table.

Drag the lookup column onto the form.

Save and publish the form.

4. Test in a Model-Driven App

Open a record of the related table in your app.

The lookup field should now allow you to search and select records from the virtual table.

Remember: You can’t create or edit virtual table records from here — only select existing ones.

Limitations & Tips

Read-only: You can’t update virtual table data from Dataverse.

Performance: Lookup search performance depends on the external data source speed.

Filtering: You can use view filters on the virtual table to limit lookup results.

Security: Access to the virtual table data is controlled by Dataverse security roles and the external data source permissions.

✅ Example Use Case:

You have a SQL table of “Vendors” as a virtual table, and you want to select a vendor in a “Purchase Order” Dataverse table form. You create a lookup relationship from Purchase Order → Vendor (virtual table) and add it to the form.

If you want, I can give you a diagram showing how the virtual table lookup relationship works in Dataverse so it’s easier to visualize.

Do you want me to prepare that?