cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Patch edits and new records from collection to SQL table

Hello,

 

I'm creating a canvas app to record student attendance at our two nursery schools.  The attendance statuses are accumulated in a collection (colAttendanceRoster) and I have a button to save the data all at once to the Azure SQL database.

 

I tried patching in bulk first, but had problems because colAttendanceRoster has both records to edit and records to add to the SQL table.  (This line works for edits, but errors if there are records to add.)

Patch('bpn.AcademyAttendance',

    ShowColumns(colAttendanceRoster, "ProgramSubTypeKey", "ClassroomKey", "PersonKey", "AttendDate", "AttendStatus"));

 

So instead, I tried to separate it by creating a collection of records to edit (colPatchEdit) and a collection of records to create (colPatchAdd)... and then do two patch statements.

 

It seems to work when I play it - both edits and adds are reflected in the Azure SQL table.

 

However, when I return to the app, there is an error warning on the save icon:

 

BPNJMC1_0-1628614877069.png

 

And the line to edit existing records is underlined in red:

 

BPNJMC1_1-1628614998084.png

With the error "The data returned by the service is invalid."

 

Does anyone know what is causing this error?   Or if there a more efficient way to do this?

 

I've pasted the code below.

 

Thanks,

Jill

 

 

// collect records to be edited (if person key exists in colAttendanceTaken)
Clear(colPatchEdit);
Collect(colPatchEdit,
    ForAll(
        Filter(colAttendanceRoster, PersonKey in colAttendanceTaken.PersonKey),     
        {
            ProgramSubTypeKey: ProgramSubTypeKey, 
            ClassroomKey: ClassroomKey,
            PersonKey: PersonKey,
            AttendDate: AttendDate,   
            AttendStatus: AttendStatus                  
       }
    )
);  

// edit existing records
Patch('bpn.AcademyAttendance', colPatchEdit);

// collect records to be added (if person key does not exist in colAttendanceTaken)
Clear(colPatchAdd);
Collect(colPatchAdd,
    ForAll(
        Filter(colAttendanceRoster, !(PersonKey in colAttendanceTaken.PersonKey)),     
        {
            ProgramSubTypeKey: ProgramSubTypeKey, 
            ClassroomKey: ClassroomKey,
            PersonKey: PersonKey,
            AttendDate: AttendDate,   
            AttendStatus: AttendStatus
        }
    )
);  

// create new records
ForAll(colPatchAdd,
    Patch(
        'bpn.AcademyAttendance', 
        Defaults('bpn.AcademyAttendance'),
        {
        ProgramSubTypeKey: ProgramSubTypeKey, 
        ClassroomKey: ClassroomKey,
        PersonKey: PersonKey,
        AttendDate: AttendDate,   
        AttendStatus: AttendStatus
        }
    ) 
);

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

@BPNJMC1 

If you are storing your primary key in the collection for edit records and a blank for the primary key for the new records, then you only need one collection.

Also, your ForAll's are backward in that you are trying to use them as a For/loop rather than as a Table function which they are.  These will perform poorly in your app.

 

I cannot tell from your formulas what your primary key is, so I will assume for the purposes of this response to be ID.

 

Please consider changing you Formula to the following:

Patch('bpn.AcademyAttendance', colAttendanceRposter)

Again, if the column names are identical to the datasource and the primary key is blank for new records and a valid number for existing, then this is all you need.

 

 I hope this is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

4 REPLIES 4

@BPNJMC1 

If you are storing your primary key in the collection for edit records and a blank for the primary key for the new records, then you only need one collection.

Also, your ForAll's are backward in that you are trying to use them as a For/loop rather than as a Table function which they are.  These will perform poorly in your app.

 

I cannot tell from your formulas what your primary key is, so I will assume for the purposes of this response to be ID.

 

Please consider changing you Formula to the following:

Patch('bpn.AcademyAttendance', colAttendanceRposter)

Again, if the column names are identical to the datasource and the primary key is blank for new records and a valid number for existing, then this is all you need.

 

 I hope this is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Hi @RandyHayes,

 

colAttendanceRoster has a few extra columns that are not saved to the SQL table.  So I had originally tried:

 

Patch('bpn.AcademyAttendance', 
    ShowColumns(colAttendanceRoster, 
        "ProgramSubTypeKey", 
        "ClassroomKey", 
        "PersonKey", 
        "AttendDate", 
        "AttendStatus"
    )
);

If(!IsEmpty(Errors('bpn.AcademyAttendance')),
    Notify("Save error." & Concat(Errors('bpn.AcademyAttendance'), Column&": "&Message), 
        NotificationType.Error, 5000),
    Notify("Successfully Saved.", 
        NotificationType.Success, 2000);
);

 

However, it was only saving the edits to the table and was not adding the new records.

(and it showed no error notification to the user)

 

The primary key is composite:

BPNJMC1_0-1628623077253.png

Could the fact that the primary key is composite be causing the problem?  It sounds like I need to create an Identity Column (GUID) for the primary key and change the current composite primary key to be a unique index instead.

 

Jill

 

 

 

@BPNJMC1 

To be honest, I am not sure how it will respond to a composite key.  I would suggest a autoincrementing primary key.

Then, if your primary ID key is blank, it will create the records, and if it is supplied, then it will update them.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

@RandyHayes ,

 

Changing the primary key (so that it was no longer composite) worked - thank you very much for your help!

 

J

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,543)