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

Powerapps issues in using Patch & Lookup Function

Hi all,

 

Need help on this patch & lookup function by matching the uniqueid the rest should in same row.

 

the first query will update the assign date, unique_id to whom allocated is updating in SP correctly

the second query by lookup the unique_id the rest of should be update in same row in SP.

 

i have enclosed the form pic and sharepoint output pic for your reference.

 

This is my Query

The first query is working fine

Patch(Single_PP_Req_EU,Defaults(Single_PP_Req_EU),{Unique_ID:Concatenate(DataCardValue1,Left(User().FullName,4),"-",Text(Now(),"ddmmyy-hhmmss")),Allocated_To: User().FullName,ASSIGN_DATE:Text(Now(),"mm/dd/hhhh hh:mm:ss")});

 

The second patch is updating twice in SP

Patch(Single_PP_Req_EU,
LookUp(Single_PP_Req_EU, Unique_ID=DataCardValue1.Text),
{Requestor_Name: DataCardValue38.Text})

 

Thanks

Jawahar

10 REPLIES 10

@Jawaharprem 

Why use a form and Patch instead of just SubmitForm(). 

v-liwei-msft
Community Support
Community Support

Hi @Jawaharprem 

 

According to the first formula you provided, Unique_ID is concatenated by DataCardValue1.Text and other text.
So in the second formula, LookUp searches for Unique_ID based on DataCardValue1.Text and the result is empty, Patch will add new record instead of update.
You can modify the second formula to:

Patch(Single_PP_Req_EU,
LookUp(Single_PP_Req_EU, DataCardValue1.Text in Unique_ID),
{Requestor_Name: DataCardValue38.Text})

 

Best Regards,

Levi

Hi, Bcz there is a box mentioned completed date, when i click submit button the current date and time should be update in complete box hence, it is possible in submit form()..

Hi Thanks, Iam Getting Delegation warning on bolded and under line item

 

Warning - "Delegation warning. The highlighted part of this formula might not work correct with column unique_id with large data set."

 

Patch(Single_PP_Req_EU,
LookUp(Single_PP_Req_EU, DataCardValue1.Text in Unique_ID),
{Requestor_Name: DataCardValue38.Text}) 

Hi @Jawaharprem 

 

I think you can try this:

Patch(Single_PP_Req_EU,
LookUp(Single_PP_Req_EU, Concatenate(DataCardValue1,Left(User().FullName,4),"-",Text(Now(),"ddmmyy-hhmmss"))=Unique_ID),
{Requestor_Name: DataCardValue38.Text})

 

Best Regards,

Levi

Hi Thanks for your time, no errors but requestor name is not updated...

poweractivate
Most Valuable Professional
Most Valuable Professional

@Jawaharprem 

 

What's probably happening is that the second Patch will create a new Record with an empty Unique_ID when the match of an empty Unique_ID is not found, which might be happening somehow. You need to explicitly tell your app not to do this by rewriting your formula accordingly, especially the second Patch in particular. 

 

Rewrite the Patches to

1. 

 

Patch(Single_PP_Req_EU,{Unique_ID:Concatenate(DataCardValue1,Left(User().FullName,4),"-",Text(Now(),"ddmmyy-hhmmss")),Allocated_To: User().FullName,ASSIGN_DATE:Text(Now(),"mm/dd/hhhh hh:mm:ss")});

 

and

2.

 

With
(
   {_myRecord:LookUp(Single_PP_Req_EU, Unique_ID=DataCardValue1.Text)}
   ,If
   (
      !IsBlank(_myRecord)
      ,Patch
      (
          Single_PP_Req_EU
         ,{
             Unique_ID=_myRecord.Unique_ID
            ,Requestor_Name: DataCardValue38.Text
          }
      )
      ,Notify("No record found with ID=" & DataCardValue1.Text,Error)
      
   )
)

 

Does it work now and does it now stop the second record with no Unique_Id from being created on the 2nd Patch above especially? 

 

If not, check the below for an improved version - it may not work properly if you have a record with a Unique_ID
that is blank - you may need to delete that Record first and try again.


If the above works, you can improve the above further by doing this:

 

With
(
    {_myDCVOneText: DataCardValue1.Text}   
	If
	(   
	    IsBlank(_myDCVOneText)
	   ,Notify("DataCardValue1.Text cannot be blank",Error)	
	   ,With
		(
		   {_myRecord:LookUp(Single_PP_Req_EU, Unique_ID=_myDCVOneText)}
		   ,If
		   (
			  !IsBlank(_myRecord)
			  ,Patch
			  (
				  Single_PP_Req_EU
				 ,{
					 Unique_ID=_myRecord.Unique_ID //or just use _myDCVOneText instead of _myRecord.Unique_ID here
					,Requestor_Name: DataCardValue38.Text
				  }
			  )
			  ,Notify("No record found with ID=" & _myDCVOneText,Error)
			  
		   )
		 )
    )
)​

 

or if you prefer it,

 

With
(
    {_myDCVOneText: DataCardValue1.Text}   
	If
	(   
	    IsBlank(_myDCVOneText)
	   ,Notify("DataCardValue1.Text cannot be blank",Error)	
	   ,If
	   (
		  !IsBlank(LookUp(Single_PP_Req_EU, Unique_ID=_myDCVOneText))
		  ,Patch
		  (
			  Single_PP_Req_EU
			 ,{
				 Unique_ID=_myDCVOneText
				,Requestor_Name: DataCardValue38.Text
			  }
		  )
		  ,Notify("No record found with ID=" & _myDCVOneText,Error)
		  
	   )
		 
    )
)​

 

If the above works even better, you can try and find out why you are trying to send the Patch when DataCardValue1.Text could be Blank or have no value, and try to not do that anymore.

 

Even if you do find the root cause, the above version might help you the developer, and even an end user, understand why that happened and prevent it from happening - so the underlying cause can be ignored and left like that too if you want and if it's intended.

 

Even if you know the underlying cause, you still want to make sure you get no new Records created with an empty Unique_ID under any circumstances so you don't get that bizarre new record with an empty Unique_ID. You also may not want arbitrary records created with arbitrary ID's provided in DataCardValue1.Text based on what it seems like you're doing.

 

If you like the above, but don't want to see any notification messages, replace the Notify functions with either just false or Blank() depending on what property you are putting this in to make it not do anything on those If branches - usually it's probably false if it's, for example OnSelect

 

With
(
    {_myDCVOneText: DataCardValue1.Text}   
	If
	(   
	    IsBlank(_myDCVOneText)
	   ,false //Notify("DataCardValue1.Text cannot be blank",Error)	
	   ,If
	   (
		  !IsBlank(LookUp(Single_PP_Req_EU, Unique_ID=_myDCVOneText))
		  ,Patch
		  (
			  Single_PP_Req_EU
			 ,{
				 Unique_ID=_myDCVOneText
				,Requestor_Name: DataCardValue38.Text
			  }
		  )
		  ,false //Notify("No record found with ID=" & _myDCVOneText,Error)
		  
	   )
		 
    )
)​

 

Note that the above version may cause you not to understand why your Patch isn't working in some scenarios - change it back to the Notify functions if you want it to tell you why it is not patching it. once you  don't want it to tell you anything anymore, just change them back to false.

 

See if this works for you @Jawaharprem 

Hi, I worked on these but only first patch is working, for patch 2 lookup uniqueid should update, the other cards  and i have mentioned a unique_id card in powerapps form id is not listed there, updating in SP only hence the other card are unable to match by the unique id, i feel sorry to disturbing thanks..

v-liwei-msft
Community Support
Community Support

Hi @Jawaharprem 

 

Could you please tell me:
When you use

Patch(Single_PP_Req_EU, LookUp(Single_PP_Req_EU,DataCardValue1.Text in Unique_ID),{Requestor_Name: DataCardValue38.Text}),

was Requestor_Name successfully patched?

 

Best Regards,

Levi

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 (721)