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 / Bug in patch towards d...
Power Apps
Unanswered

Bug in patch towards dataverse with required field

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Background
We have a canvas app where we are generating new items based on which template the user selected.
The generated items based on the template is stored in a collection and shown to the user.


The bug

The problem is that we get an error saying title is required when patching the collection to dataverse table.
BUT we have already included the title in the patch. The data gets saved, but the error still occurs indicating title is requried.

I have the same patching scenario in a SharePoint Custom Forms App and it works against SP but not against dataverse).
(Power Apps version 3.23011.19)

Dataverse table
To be able to reprocuce the bug I created a simple dataverse table (called "TestPatchBugTable" below) with only one column "Title" of type text and set to required. (I changed name of the primary column "name" to "Title" in the dataverse table)


Code

The following line below gives error indicating that the title column is required.
Patch(TestPatchBugTable; collDataToPatch);;
.. and as you can see there is only one column set in the patch, the title column, which causes the patch collection to fail.

// 1. Get data from a table with templates
Collect(collTemplate; 
 Table(
 {
 Title: "From Template 1" 
 };
 {
 Title: "From Template 2" 
 };
 {
 Title: "From Template 3" 
 }
 )
);;


// 2. For all items in template add an item in collection
Clear(collDataToPatch);;
ForAll(collTemplate; 
 Collect(collDataToPatch; Defaults(TestPatchBugTable); 
 { 
 Title: ThisRecord.Title & " - Test add to collection"
 }
 )
)
;;


// patch collection from template – gives error
Patch(TestPatchBugTable; collDataToPatch);;

 

Categories:
  • Bilakanti Profile Picture
    1,226 on at

    @Anonymous I think when you're patching the collection, the schema will be considered and the name that you're using in the collection and the schema name should match.

  • VEEROCHET Profile Picture
    18 on at

    I have the same issue. And the field from the collection already has identical names to the table's field.

    The error is still coming up. The data is saved, but the error is showing.

    The field should not even be required in the first place since the patch is just an update of existing records.

     

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

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 220 Super User 2026 Season 2

#2
WarrenBelz Profile Picture

WarrenBelz 189 Most Valuable Professional

#3
Mohsin Ali Profile Picture

Mohsin Ali 139

Last 30 days Overall leaderboard