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 / Error: Value must be d...
Power Apps
Suggested Answer

Error: Value must be data entity record.

(0) ShareShare
ReportReport
Posted on by 4
I have one dataverse table which has 3 columns Section, SubSection and Elements (all text types). This table is filled with data where for each section there can be multiple subsections and same way for each subsections there can be multiple elements.
Now I created another table where i added three columns Section, Subsection and Elements and all have lookup from first table.
Now I added this second table in form. I want to show all three columns should have distinct values in form on the basis of data from first form.
I added this simple formula to DataCardValue26 combobox which is not showing any error but when I tries to submit the form it is throwing error on same datacard: Value must be data entity record.
I am using Modern controls.
Distinct(([@'Role Requests'].'odms_ODELSection'),ODELSection.Section)
The DataCardValue26 field is :
 
The update property of Datacard is : 
DataCardValue26.Selected
 
If I replace
DataCardValue26.Selected.Value then error on .Value part shows "Expected Record Value" so i didnt change.
I have the same question (0)
  • Suggested answer
    mrcwojcik Profile Picture
    68 on at
    Form must submit a record, but distinct returns a table of text values. That's why you have error.
     
    You would need to change:
     
    1. Items attribute:
     
     
    With(
        { g: GroupBy('Role Requests', "odms_ODELSection", "grp") },
        ForAll(g, First(grp).odms_ODELSection)
    )
     
    Then you can change what is displayed and searched.



    If this post helped you, please click Accept as solution ✅. This allows other community members with a similar question to find the answer more quickly. If you found the information useful in other ways, a Like 👍 or 'Yes' to Was this reply helpful? is always appreciated!
  • ashokpershad Profile Picture
    4 on at
    @mrcwojcik Thank you for your reply. 
    For me "odms_ODELSection" is not showing up as column name when writing the formula though the name is correct. I even remove the inverted commas. 
    My formula:
    With({d:GroupBy('Role Requests','odms_ODELSection', "grp")},ForAll(d, First(grp).'odms_ODELSection'))
     
  • Kalathiya Profile Picture
    1,485 Super User 2026 Season 1 on at
    Hello @ashokpershad
     
    Your Section Items Property, 
    Distinct(Choices([@'Role Requests'].'odms_ODELSection'),Name) //Name - Use your Primary column name from Parent table..
    Update Item Property, 
    LookUp(Choices([@'Role Requests'].'odms_ODELSection'),Name = DataCardValue26.Selected.Value)
    //Name - Replace Name with the primary column of your first Dataverse table (the column that uniquely identifies the record).
    If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.
    ---------------------------------------------------------------------------------
     
    📩 Need more help? Mention@Kalathiya anytime!
    ✔️ Don’t forget to Accept as Solution if this guidance worked for you.
    💛 Your Like motivates me to keep helping!

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 542 Most Valuable Professional

#2
Haque Profile Picture

Haque 206

#3
Kalathiya Profile Picture

Kalathiya 201 Super User 2026 Season 1

Last 30 days Overall leaderboard