Microsoft Dynamics 365 | Integration, Dataverse...

Virtual table on sql view error on single report

(2) Share

Report

Posted on by GianlucaN

Hello,

I've made a virtual table based on SQL View.

When I open the virtual entity on Dynamics, all record are visualized correctly.

But when I try to open single record by clicking on my /All record/ view of my virtual table, I've this error.

APIM request was not successful : StatusCode : BadRequest, Reason : The specified item 'db4383b4-0684-4c49-9475-384dcae98f0c' is not found.

Somebody have an idea to resolve this problem?

Thanks in advance

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Partner,

Maybe you can refer to the following link, check that the GUID field is marked as Primary Key:

https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Issue-with-Virtual-Table-using-Virtual-connectors-for-Dataverse/td-p/1721336

Also, you can refer to following links to check all possible reasons:

https://carldesouza.com/7-reasons-virtual-tables-arent-working-in-the-power-platform/https://carldesouza.com/7-reasons-virtual-tables-arent-working-in-the-power-platform/

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/limits-tshoot-virtual-tables?tabs=sql

I hope you can verify my answer if it helps you! If you have any questions, please feel free to contact me.
Regards,
Leah

Was this reply helpful? Yes No
CU27040910-4 4 on at

Like (0)

Report
Copy link

Link copied!

I'm having the same issue.

Were you able to get around it?

I can't find any solutions anywhere.

Was this reply helpful? Yes No
DM-28111358-0 4 on at

Like (0)

Report
Copy link

Link copied!

I'm having this same problem right now. If you have any updates on the problem, I would appreciate your comments.

In my case, I'm using a view from source with a number primare key.

Was this reply helpful? Yes No
DM-28111358-0 4 on at

Like (0)

Report
Copy link

Link copied!

I'm having this same problem right now.

About your suggest to use a primary key, it is imposible to use at level of SQL Sever views. Actually I'm using a number value to use as a primary key from view source. But in the case of Gianluca, he is using GUID and he is getting the same problem.

I don know if configuring a GUID instead a number key is the solution.

Was this reply helpful? Yes No