{"title":"Create synthetic table relationships","url":"https://jonas-paprotka.de/docs/dev-itpro/powerplatform/create-synthetic-relationships-virtual-tables/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/powerplatform/create-synthetic-relationships-virtual-tables, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/powerplatform/create-synthetic-relationships-virtual-tables","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn to configure and validate links between Dataverse native tables and Business Central virtual tables.","date":"2025-09-17","meta":{"topic":"concept-article"},"outline":[{"level":2,"title":"When not to use synthetic relationships","slug":"when-not-to-use-synthetic-relationships","at":178,"chars":457},{"level":2,"title":"Create synthetic relationship between native and virtual table","slug":"create-synthetic-relationship-between-native-and-virtual-table","at":635,"chars":2581},{"level":2,"title":"Known limitations","slug":"known-limitations","at":3216,"chars":274},{"level":2,"title":"Related information","slug":"related-information","at":3490,"chars":644}],"text":"This article provides step-by-step instructions on when and how to set up and configure synthetic relationships using virtual tables for\nBusiness Central in Microsoft Dataverse.\n## When not to use synthetic relationships\nEven though it's possible, we don't recommend creating synthetic relationships between two virtual tables. If you need to do it, create a ../developer/devenv-develop-custom-api with the correct relationships. They're reflected inside Microsoft Dataverse. Learn more about how internal API relationships transform into virtual table relationships powerplat-entity-modeling#native-tabletonative-table-relationships.\n## Create synthetic relationship between native and virtual table\nConsider an example where you want to show sales orders from the dyn365bc_salesorder_v2_0 virtual table inside the native Account table in Dataverse.\n1. Sign in to Power Apps<https://make.powerapps.com/> and switch to the environment that contains the table.\n1. Create a foreign key in Account table:\n 1. Select Tables > Account > Keys.\n 1. Select New key, then enter a name and display name for the key the Key pane.\n 1. Select the columns needed for the relation. You can select one, two, or three columns to use in the native to virtual table relation.\n 1. Select Save to create the key.\n ![Screenshot of the Keys view in Dataverse showing creation of a new key for synthetic relationship.]<https://learn.microsoft.com/dynamics365/business-central/dev-itpro/powerplatform/media/create-synthetic-relationships-virtual-tables/image1.png#lightbox>\n1. Open Business Central Configuration app (from the navigation pane, select Apps > Business Central Configuration).\n1. Select Table Relations > New to open the New Business Central Table Relation page.\n ![Screenshot of the Business Central Configuration app General tab for defining a synthetic relationship showing native table and key fields.]\n1. On the General tab, provide the following information:\n Field|Description|Example\n -|-|-\n Relation Name|A custom name for this synthetic relationship.|dyn365bc_account2salesorder\n Native Table|The logical name of native table you want to use. Find this value in the table properties.|Account\n Native Table Key|The name of the key|crec7_key_for_relation_with_bc_sales\n Virtual Table|The logical name for the virtual table you want to use. Find this value in the table properties.|dyn365bc_salesorder_v2_0\n> TIP\n> To view the logical name in the table properties, open the table, select Properties, and then expand Advanced options in the Edit table pane.\n1. On the Mapping tab, provide column mapping between the native table and one or more virtual table columns. All columns included in the table key (defined in step 1) must be mapped. Use their logical names.\n ![Screenshot of the Business Central Configuration app General tab for defining a synthetic relationship showing native table and key fields.]\n1. Select Save to validate and save the relationship.\n1. Test the relationship. For example, in Power Apps, add a subgrid component and set the Sales Orders as related relationship. See https://learn.microsoft.com/power-apps/maker/model-driven-apps/form-designer-add-configure-subgrid#add-a-subgrid-component.\n## Known limitations\n You can't edit an existing synthetic table relationship. You must remove it and then recreate it with the changes.\n If you refresh a table that changes columns included in the mapping, an error occurs. You must remove the synthetic relationship first.\n## Related information\nUse synthetic relationships to expose more Business Central data in Dataverse<https://learn.microsoft.com/dynamics365/release-plan/2024wave1/smb/dynamics365-business-central/use-virtual-tables-expose-more-business-central-data-dataverse>\nOverview - Integrating Business Central with Microsoft Dataverse<../developer/dataverse-integration-overview>\nMicrosoft Power Platform Integration with Business Central<powerplat-overview>\nApplication Lifecycle Management for Solutions that use Virtual tables<powerplat-app-lifecycle-management>\nBusiness Central and Dataverse Admin Reference<powerplat-admin-reference>\npowerplat-faq"}