undefined

Hello Sam67548990,

Since the relationship has been created successfully, the issue is likely occurring when Dataverse attempts to retrieve the related records through the virtual table provider.

A few things I'd recommend checking:

• Verify that the Primary Key mapped for the Fabric virtual table is truly unique and matches the data type expected by the Dataverse lookup.

• Ensure the Primary Name column is also mapped correctly, as lookups rely on both the primary key and primary name.

• Confirm that the account accessing the virtual table has the necessary permissions on both the Dataverse table and the underlying Fabric data source.

• Review the browser's Developer Tools (Network tab) or the Power Platform Monitor to inspect the failed APIM request. This often provides a more detailed error than the generic ISV message.

If the relationship is created but both the lookup and subgrid fail with "APIM request was not successful", it may indicate a limitation or issue with the current Fabric Virtual Table provider rather than the relationship itself.

Could you also confirm:

• Is the Fabric source a Lakehouse or a Warehouse?

• Are you using the SQL Analytics Endpoint or another endpoint for the virtual table?

This information will help narrow down the root cause.

Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant

💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.