web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Issue with Virtual Tab...
Power Apps
Unanswered

Issue with Virtual Table using Virtual connectors for Dataverse

(0) ShareShare
ReportReport
Posted on by 51

Hi, I have a very simple scenario with a SQL Database located in a On-premises server. I followed the Create virtual tables using virtual connectors (preview) (Microsoft Dataverse) - Power Apps | Micros... and managed to connect to the server and everything seems to work by the end of the tutorial, but when I try to do any CRUD operation I got an error message as follows:

 

The specified domain does not exist or cannot be contacted

Error Code: 2147746340
Session Id: guid
Activity Id: guid
Timestamp: date

APIM request was not successful : BadRequest : The specified item 'id' is not found. inner exception: The specified item 'id ' is not found.

 

When I create or update the item the operation is done but still the error message shows up. If I try to use the table in any Model-driven app only create and list operations work, however after creation the detail view fails to load. I cannot get details, actually the details appears for a few seconds and the error message shows up with the close action.

 

I tried the tutorial several times, and use two different servers, two different databases and several different tables with no luck. Does anyone have an idea of what I did wrong, because I see many people who has followed the tutorial and have the virtual tables working.

I have the same question (1)
  • Aspire_Alex Profile Picture
    8 on at

    I'm experiencing the same issue, table/list views work fine but open the record and you get that not found error.  Did you find a solution?

     

    I tried doing a SQL trace and I can see 'MashupEngine' running the query for the list, but no queries for the data to populate the form; so it looks the form isn't hitting the on-premise SQL server at all.

  • Eliel Aguilera Profile Picture
    51 on at

    Hi, yes, the problem was the IDs, I had to use an GUID column as ID and that solved the problem. It seems not to be part of the documentation but the ID field should be a GUID as in Dataverse.

  • Aspire_Alex Profile Picture
    8 on at

    I am already using a GUID column as the ID 😞 

  • Eliel Aguilera Profile Picture
    51 on at

    Hi, sorry for the late response but, can you make sure the field is also marked as Primary Key?

  • Aspire_Alex Profile Picture
    8 on at

    It is the Primary Key, yes.

  • Eliel Aguilera Profile Picture
    51 on at

    What I mean is, it is the field marked as PK in the table? I did forgot to mark my field as PK (I did only used IDENTITY(1,1) and I did not created the primary key constraint).

  • Aspire_Alex Profile Picture
    8 on at

    It's definitely a PK (uniqueidentifier) in the source SQL table.

  • PaddyWann Profile Picture
    101 on at

    same issue please help

  • leratoTSOE Profile Picture
    2 on at

    Hi, did u managed to resolve. please advice

  • Ali7752 Profile Picture
    26 on at

    what was the exact solution here?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
Vish WR Profile Picture

Vish WR 414

#2
Valantis Profile Picture

Valantis 387

#3
timl Profile Picture

timl 344 Super User 2026 Season 1

Last 30 days Overall leaderboard