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

Patch Dataverse Table with Lookup Columns from Collection

I have one Table in Dataverse (Manhours) with following columns:

ashokpershad_2-1635839721793.png

 

Now I used one FORM with this table as Datasource. When I press one submit button after filling details in this form I am creating one collection (displayed in Gallery5) where I am storing all  FORM submit entries. Please note this Submit button actually not for SUBMITFORM function. It is only for submitting new entries in collection.

Gallery5:

ashokpershad_1-1635839285445.png

Now I want to Patch this Gallery back to my Dataverse Table using this ForAll and Patch functions. 

I used Following Formula:

 

 

 

ForAll(Gallery5.AllItems, Patch(Manhours, Defaults(Manhours), {WOrder:glry5WO.Text, 'Lab Supervisor':LookUp(Manhours, 'Lab Supervisor'.Supervisor = glry5Sup.Text), 'Service Engineer': LookUp(Manhours, 'Service Engineer'.'Engineer Name' = glry5eng.Text), 'Date Started':glry5DS, 'Date Completed': glry5DE, 'Actual Work Hours': glry5AH.Text, Remarks: glry5Remarks.Text}))

 

 

 

But this formula is showing following error:

ashokpershad_0-1635841333172.png

 

What formula shall I use? 

 

I hope its clear.

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Hello @ashokpershad,

 

Can you please try the same below

 

ForAll(Gallery5.AllItems, Patch(Manhours, Defaults(Manhours), {WOrder:glry5WO.Text, 'Lab Supervisor':LookUp(Manhours, Name = glry5Sup.Text), 'Service Engineer': LookUp(Manhours, Name = glry5eng.Text), 'Date Started':glry5DS, 'Date Completed': glry5DE, 'Actual Work Hours': glry5AH.Text, Remarks: glry5Remarks.Text}))

 

Name --> It should be Primary Name Field in the Lookup Entity

 

Please mark as Answer if it is helpful and provide Kudos


Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

 

View solution in original post

dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @ashokpershad ,

 

Please review the following article and try doing a validation or handling the errors and see if you get better information.  

https://matthewdevaney.com/power-apps-patch-function-error-handling/ 

 

Thanks,

 

Drew

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

View solution in original post

11 REPLIES 11
dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @ashokpershad ,

 

Looking at your patch function should your lookups be actually going against the User table?

ForAll(Gallery5.AllItems, Patch(Manhours, Defaults(Manhours), {WOrder:glry5WO.Text, 'Lab Supervisor':LookUp(Users, 'Full Name' = glry5Sup.Text), 'Service Engineer': LookUp(Users, 'Full Name' = glry5eng.Text), 'Date Started':glry5DS, 'Date Completed': glry5DE, 'Actual Work Hours': glry5AH.Text, Remarks: glry5Remarks.Text}))

Not sure if the above is the right adjustment but overall you have two lookup columns for the Lab Supervisor and Engineer and I would expect you are trying to find the Users table value for these to populate in the field?  In this case I think your lookup needs to go against that table vs. your Manhours table.

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.


Thanks,


Drew

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

Dear @dpoggemann 

Someone suggested me this way to deal with Lookup when patching but it seems this is not the right way. Ignore my Formula... Could you please suggest what should be the best solution to patch this collection back to ManHours table in dataverse ?

dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @ashokpershad ,

 

Are the lookup columns for the engineer and the supervisor to the Users table?  If they are you might want to try the code I put in there above...  


A good article showing how to patch some of the more complex types is here:  http://powerappsguide.com/blog/post/dataverse-how-to-patch-the-5-most-complex-data-types 

 

Hope this helps.  Please accept if answers your question or Like if helps in any way.


Thanks,

Drew

 

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

Hello @ashokpershad,

 

Can you please try the same below

 

ForAll(Gallery5.AllItems, Patch(Manhours, Defaults(Manhours), {WOrder:glry5WO.Text, 'Lab Supervisor':LookUp(Manhours, Name = glry5Sup.Text), 'Service Engineer': LookUp(Manhours, Name = glry5eng.Text), 'Date Started':glry5DS, 'Date Completed': glry5DE, 'Actual Work Hours': glry5AH.Text, Remarks: glry5Remarks.Text}))

 

Name --> It should be Primary Name Field in the Lookup Entity

 

Please mark as Answer if it is helpful and provide Kudos


Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

 

dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @rampprakash,


The lookup for the users wouldn't be to the Manhours table I wouldn't think...  I assume they would be looking at the Users table for the Supervisor and Engineer so that is why I changed the code to do lookup like the following for those two that are like this one...  Does this make sense as the right change to you?  

'Service Engineer': LookUp(Users, 'Full Name' = glry5eng.Text)

Thanks,

Drew

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

Hello @dpoggemann,

 

If @ashokpershad need to fetch User then your code is perfectly correct. If he is expecting from custom entity then he can look at my code

Dear @rampprakash  and @dpoggemann 

Thank you for your replies. 

Let me clarifies few things. Both my Supervisor and Engineer tables are custom tables with data like name, emails company etc. Have a look at below tables screenshot:

SUPERVISOR TABLE:

ashokpershad_0-1635922751817.png

ENGINEER TABLE:

ashokpershad_1-1635922805077.png

 

@rampprakash  I have tried adding same formula as you advised:

 

 

ForAll(Gallery5.AllItems, Patch(Manhours, Defaults(Manhours), {WOrder:glry5WO.Text, 'Lab Supervisor':LookUp(' Abc Supervisors', Supervisor = glry5Sup.Text), 'Service Engineer': LookUp('Service Engineers', 'Engineer Name' = glry5eng.Text), 'Date Started':glry5DS, 'Date Completed': glry5DE, 'Actual Work Hours': glry5AH.Text, Remarks: glry5Remarks.Text}))

 

 

There is NO errors now except one delegation warning. How can we remove this warning.

 

ashokpershad_1-1635925275392.png

 

Only thing now, the data is not patching in the Manhours Table. Table is still not updating any data after pressing this Patch button.

In Manhours I have total 7 columns which I am already using in Patching. 

Thank you for your patience but this issue is taking too long to resolve.

 

 

dpoggemann
Most Valuable Professional
Most Valuable Professional

Hi @ashokpershad ,

 

I would try the following to break this down:

Create this outside of the ForAll:

1.  Add fields to your Canvas App to store Lookup values of your Engineer and Supervisor

2.  Manually pass in the values for one of the rows to these Lookups and verify they return what you are expecting

3.  Set all the fields in the patch manually from values of one of the records and verify you can get this patch to work. 

4.  Once you have patch working for 1 record then we can analyze the ForAll.

 

Hope this helps to identify the source of the issue.


Thanks,

 

Drew

 

 

Hope this helps. Please accept if answers your question or Like if helps in any way.
Thanks,
Drew

@dpoggemann 

I tried but there is some error coming:

ashokpershad_0-1635935013180.png

This error coming after i press the Patch submit button. Before pressing button this error is not showing in formula section.

Everything seems fine but still not resolved.

Sorry now its becoming very frustrating.

Thanks

 

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 (2,479)