cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GavsApps
Frequent Visitor

Every time, I am trying to save the record using below code getting runtime error " The data source supplied to the function is invalid" Please suggest here. I am trying to bind the value into to collection rather than directly into data source to in order to increase the performance of app.

Set(
varAuditReq,
Patch(
colProviders,
Defaults(colProviders),
{Provider: ComboBox4.Selected.Result},
{Center: DataCardValue2.Text},
{DateOfAudit: DataCardValue44.SelectedDate},
{OverallScore: Value(lblChronicCumulative.Text)},
{Patient: DataCardValue18.Text},
{DOB: DataCardValue20.SelectedDate},
{DateOfService: DataCardValue22.SelectedDate},
{TCMTOCPatient: DataCardValue56.Text},
{TCMTOCDOB: DataCardValue58.SelectedDate},
{TCMTOCDateOfService: DataCardValue59.SelectedDate},
{AcutePatient: DataCardValue68.Text},
{AcuteDOB: DataCardValue70.SelectedDate},
{AcuteDateOfService: DataCardValue71.SelectedDate},
{HealthMainPatient: DataCardValue80.Text},
{HealthMainDOB: DataCardValue82.SelectedDate},
{HealthMainDateOfService: DataCardValue83.SelectedDate}
)
);

ForAll(
galChronic.AllItems,
Patch(
colChronicResults,
{
ProviderID:varAuditReq.ID,
ElementsHeader: Label6.Text,
Elements: Title2_4.Text,
Y_x002f_N: RadioChronicYesNoOther.Selected.Answer,
Comments: txtComments_4.Text,
Score: Value(txtChronicScoreYesNoOther.Text),
CategoryScore: Value(lblChronicCategory.Text),
WeightedScore: Value(lblChronicWeighted.Text),
CumulativeScore: Value(lblChronicCumulative.Text)
}
)
);

2 ACCEPTED SOLUTIONS

Accepted Solutions
BrianS
Super User
Super User

I could be wrong but I would try the syntax in the second Patch for both of them. In the first you are setting every field off in {} I think you should just use the {} around the grouping as you have in the second one.

View solution in original post

Hi @GavsApps ,

That is a different issue altogether to your previous two - the syntax of this code is valid

Patch(
   colChronicResults,
   ForAll(
      galChronic.AllItems,
      {
         ProviderID: varAuditReq.ID,
         ElementsHeader: Label6.Text,
         Elements: Title2_4.Text,
         Y_x002f_N: RadioChronicYesNoOther.Selected.Answer,
         Comments: txtComments_4.Text,
         Score: Value(txtChronicScoreYesNoOther.Text),
         CategoryScore: Value(lblChronicCategory.Text),
         WeightedScore: Value(lblChronicWeighted.Text),
         CumulativeScore: Value(lblChronicCumulative.Text)
      }
   )
);

 It is saying that one of the fields you are patching to is a Table - I suspect probably Y/N is a Choice column - if so

Y_x002f_N: {Value: RadioChronicYesNoOther.Selected.Answer}

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

 

View solution in original post

12 REPLIES 12
BrianS
Super User
Super User

I could be wrong but I would try the syntax in the second Patch for both of them. In the first you are setting every field off in {} I think you should just use the {} around the grouping as you have in the second one.

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @GavsApps ,

Your problem is that a collection has neither Defaults nor an ID (automatically anyway). However you can increase the performance of your Patch enormously by Patching the Table created by ForAll() rather than looping though with multiple patch instances. Example only below - you would have to create the ID somewhere - this would create new records in the data source

Patch(
   DataSource,
   ForAll(
      galChronic.AllItems,
      {
         ProviderID: ????
         ElementsHeader: Label6.Text,
         Elements: Title2_4.Text,
         Y_x002f_N: RadioChronicYesNoOther.Selected.Answer,
         Comments: txtComments_4.Text,
         Score: Value(txtChronicScoreYesNoOther.Text),
         CategoryScore: Value(lblChronicCategory.Text),
         WeightedScore: Value(lblChronicWeighted.Text),
         CumulativeScore: Value(lblChronicCumulative.Text)
      }
   )
);

also for the first piece of code to add new records to a Collection

Collect(
   colProviders,
   {
      Provider: ComboBox4.Selected.Result,
      Center: DataCardValue2.Text,
      DateOfAudit: DataCardValue44.SelectedDate,
      OverallScore: Value(lblChronicCumulative.Text),
      Patient: DataCardValue18.Text,
      DOB: DataCardValue20.SelectedDate,
      DateOfService: DataCardValue22.SelectedDate,
      TCMTOCPatient: DataCardValue56.Text,
      TCMTOCDOB: DataCardValue58.SelectedDate,
      TCMTOCDateOfService: DataCardValue59.SelectedDate,
      AcutePatient: DataCardValue68.Text,
      AcuteDOB: DataCardValue70.SelectedDate,
      AcuteDateOfService: DataCardValue71.SelectedDate,
      HealthMainPatient: DataCardValue80.Text,
      HealthMainDOB: DataCardValue82.SelectedDate,
      HealthMainDateOfService: DataCardValue83.SelectedDate
   }
);

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @GavsApps ,

Just checking if you got the result you were looking for on this thread. Happy to help further if not.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

GavsApps
Frequent Visitor

@WarrenBelz Thank you for checking, issue still persists. As per my use case(Questionnaire App using SharePoint as datasource ) I need to pass ProviderID of first patch which I am storing in variable (varAuditReq) and using it all the places where ever I need. I am still facing the same issue. 

@GavsApps ,

I would have thought you just need varAuditReq where I have ???? in the code I posted.

GavsApps
Frequent Visitor

@WarrenBelz I used varAuditReq in place of ??? and also using varAuditReq as reference to piece of code for different SP list however it didn't work. 

@GavsApps ,

I will admit, I am having more than a little difficulty visualising exactly what you are doing from what you have posted especially when the error is at data source connection rather than code level. From what I can see however, you simply need to retrieve the value to be patched into ProviderID  but you have not told me sufficient about this item to understand where you are getting this from. You are updating your Data Source with the contents of a gallery and adding this value to the relevant field. If you are storing this in a Variable, why is it not working (are you getting any errors in the code or errors following the Patch ?

My bad, I have not explained the complete context and use case. Now, I am sharing the part of logic to give you more insight. Also sharing the screenshot of error.

Set(
varAuditReq,
Collect(

colProviders,

Defaults(colProviders),
{Provider: ComboBox4.Selected.Result},
{Center: DataCardValue2.Text},
{DateOfAudit: DataCardValue44.SelectedDate},
{OverallScore: Value(lblChronicCumulative.Text)},
{Patient: DataCardValue18.Text},
{DOB: DataCardValue20.SelectedDate},
{DateOfService: DataCardValue22.SelectedDate},
{TCMTOCPatient: DataCardValue56.Text},
{TCMTOCDOB: DataCardValue58.SelectedDate},
{TCMTOCDateOfService: DataCardValue59.SelectedDate},
{AcutePatient: DataCardValue68.Text},
{AcuteDOB: DataCardValue70.SelectedDate},
{AcuteDateOfService: DataCardValue71.SelectedDate},
{HealthMainPatient: DataCardValue80.Text},
{HealthMainDOB: DataCardValue82.SelectedDate},
{HealthMainDateOfService: DataCardValue83.SelectedDate}
)
);

Patch(
colChronicResults,
//Defaults(colChronicResults),
ForAll(
galChronic.AllItems,
{
ProviderID: varAuditReq.ID,
ElementsHeader: Label6.Text,
Elements: Title2_4.Text,
Y_x002f_N: RadioChronicYesNoOther.Selected.Answer,
Comments: txtComments_4.Text,
Score: Value(txtChronicScoreYesNoOther.Text),
CategoryScore: Value(lblChronicCategory.Text),
WeightedScore: Value(lblChronicWeighted.Text),
CumulativeScore: Value(lblChronicCumulative.Text)
}
)
);

ForAll(
RenameColumns(
galTCM_TOC_1.AllItems,
"ID",
"ID2"
),
Patch(
//tblTCM_TOCResults,
colTCM_TOCResults,
//Defaults(tblTCM_TOCResults),
Defaults(colTCM_TOCResults),
{ProviderID: varAuditReq.ID},
{ElementsHeader: Label9.Text},
{Elements: Title2_6.Text},
{Y_x002f_N: RadioTCMYesNoOther.Selected.Answer},
{Comments: txtComments_6.Text},
{Score: Value(txtTCMScoreYesNoOther.Text)},
{CategoryScore: Value(LabelTCMCategory.Text)},
{WeightedScore: Value(lblTCMWeighted.Text)},
{CumulativeScore: Value(LabelTCMCumulative.Text)}
)
);
ForAll(
RenameColumns(
galAcute_1.AllItems,
"ID",
"ID3"
),
Patch(
//tblAcuteResults,
colAcuteResults,
//Defaults(tblAcuteResults),
Defaults(colAcuteResults),
{ProviderID: varAuditReq.ID},
{ElementsHeader: Label11.Text},
{Elements: Title2_7.Text},
{Y_x002f_N: RadioAcuteYesNoOther.Selected.Answer},
{Score: Value(txtAcuteScoreYesNoOther.Text)},
{CategoryScore: Value(lblAcuteCategory.Text)},
{WeightedScore: Value(lblAcuteWeighted.Text)},
{CumulativeScore: Value(lblAcuteCumulative.Text)}
)
);

Error - Invalid argument type(Table). expecting a record instead.
The function patch has some invalid arguments.

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