From 0fa164ce884c0c5a62c26acc822002291d032584 Mon Sep 17 00:00:00 2001 From: Jim Duncan Date: Wed, 19 Mar 2025 10:38:54 -0700 Subject: [PATCH] Update limits-tshoot-virtual-tables.md - SharePoint Lookup columns not supported Based on my mostly-rigorous testing, Lookup columns are not supported. They are ignored by the Virtual Table wizard and adding a Relationship after the fact does not work and results in an error. Feel free to contact me to discuss. --- .../maker/data-platform/limits-tshoot-virtual-tables.md | 1 + 1 file changed, 1 insertion(+) diff --git a/powerapps-docs/maker/data-platform/limits-tshoot-virtual-tables.md b/powerapps-docs/maker/data-platform/limits-tshoot-virtual-tables.md index 8c830b08e2..188324c398 100644 --- a/powerapps-docs/maker/data-platform/limits-tshoot-virtual-tables.md +++ b/powerapps-docs/maker/data-platform/limits-tshoot-virtual-tables.md @@ -92,6 +92,7 @@ The following are limitations for each data source. - Managed metadata - Location: coordinates - Attachment + - Lookup - SharePoint specific columns that are shown in the virtual table: - **Compliance Asset ID** is an internal column from SharePoint for tracking purposes. It can be ignored. - **ID** is the external primary key from SharePoint. It's read-only and can be ignored.