Microsoft Dynamics 365 | Integration, Dataverse...

Virtual Table Error: APIM request was not successful, no primary key

(0) Share

Report

Posted on by Pawel Szymczyk

Hi,

I'm working with Virtual Tables (entities), following documentation I have created tables using SQL Server connector.

It properly displays a grid with data, but the problem is when I try to open the item details page, which starts loading the details page and displays an error: "APIM request was not successful: BadRequest: No primary key exists in table".

But I do not understand why the error says there is no primary key if I specifically provided it during virtual table creation. I have provided Id (GUID) for "Primary key of the Virtual Entity" and Name (string) for "Primary field of the Virtual Entity".

Based on that information it did create a virtual entity, which according to documentation should work as any other table.

So my question is what can cause the problem and how can I fix it?

Thanks in advance.

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Pawel,

The following are limitations for each data source.

https://docs.microsoft.com/en-us/power-apps/maker/data-platform/create-virtual-tables-using-connectors?tabs=sql#for-each-data-source

Was this reply helpful? Yes No
Pawel Szymczyk 5 on at

Like (0)

Report
Copy link

Link copied!

Hi Leah,

Thanks for your suggestion.

Indeed its a limitation, when I directly have used a table to connect to, it was working without problems, but the idea and the problem is when using SQL view, D365 cannot see its primary key (which does not exists, cos its a view) so it prompts an error.

Was this reply helpful? Yes No
Amira Beldjilali Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hello,

Do you have a Primary Key in the SQL table?

You probably need to set it there:

ALTER TABLE ADD CONSTRAINT PRIMARY KEY ();

Regards,

Amira

Was this reply helpful? Yes No