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 Automate / Error in getting row f...
Power Automate
Answered

Error in getting row from Dataverse Table

(0) ShareShare
ReportReport
Posted on by 61

Hello,

I would appreciate any help on the following. I am trying to get a Dataverse table row by Id. The value for the Id is the value from a parameter of an Http request. The value is 'Subcategory 2'.  The Row Id field of the table is the one defined as primary key (primary name column), correct? 

The retrieval fails with ' 'Not Found' error as you can see below, although there is a record with this Id in the table. Can anybody explain why this happens and what is the entity name 'crbc1_modifyfieldses' that I see in the input parameters of Get a row by Id in the 3rd screenshot below?

 

asynadinou_1-1718708914877.png

 

asynadinou_2-1718709120628.png

 

asynadinou_0-1718708883152.png

asynadinou_3-1718709234049.png

 

 

Categories:
I have the same question (0)
  • Verified answer
    LukeMcG Profile Picture
    48 on at

    Hi @asynadinou

     

    When using the Dataverse connector, the actions will be expecting a GUID for the Row ID parameter which is not the same as the Primary Name value. This Learn page explains the difference between Primary Key and Primary Name: Table definitions in Microsoft Dataverse - Power Apps | Microsoft Learn

     

    The entity name that you see in the input parameters will be the logical name of your Dataverse table (I believe the "Deflection" table based on your screenshots), this value is based on the table name provided when the table is created and can't be changed.

     

    To get the row that you're looking for which matches the specific "Subcategory intent" text value that is passed in from your HTTP request trigger, I'd recommend using a "List Rows" action and using the "Filter Rows" input to provide an ODATA filter instead.

     

    You'll need the logical name of your "Subcategory intent" column which you should able to see in your table definition by navigating to "Columns": 

     

    LukeMcG_0-1718714949543.png

     

    Your filter should then look similar to this: 

     

    LukeMcG_2-1718715208807.png

     

  • asynadinou Profile Picture
    61 on at

    Perfect, @LukeMcG ! It worked.

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 Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 274 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 175

#3
Haque Profile Picture

Haque 166

Last 30 days Overall leaderboard