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

Custom Patch Code, If Dropdown equals Completed then patch to different source if not SubmitForm

Hi,

 

I have a form app with a flow that once the user submits task it sends the data to another list (A Completed List), however it takes 10mins sometimes to move over, i figured i can make it work another way by using the patch and an If Statment, however my attempts at coding it are at a loss,

 

So Is it possible to have an button use OnSelect if a dropdown equals say "Completed" then rather than OnSubmit Patch to another source and if anything else then just submitform? and id like it to also delete the item after onsuccess.

 

Could someone post the example code i would need?

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
poweractivate
Most Valuable Professional
Most Valuable Professional

@Questionasking 

Result working:

 

AppCompletedSample-898253-a.gif

 

 

Explanation (for the explanation it was tested with a real SharePoint List and found to be working - note that this actually differs a little bit from the attached msapp file at the bottom of this post):

 

Working SharePoint List Patch Example App (not provided as an msapp in the attachment - so see instead full explanation below, and possibly import attached msapp and adjust it using the below explanation if you want):

 

App has two Screens, Screen1 and Screen2 (Screen1 is most important - Screen2 is optional but if using exactly this specific example, both screens should be there in that case):

 

On Screen 1:

 

Screen1 OnVisible:

 

 

 

 

 

Refresh(Completed);ClearCollect(_SampleCollDef01,Split("Not Completed,Completed",","));Reset(Dropdown2);Reset(TextInput1);

 

 

 

 

In the above the most important part is just:

 

 

 

ClearCollect(_SampleCollDef01,Split("Not Completed,Completed",","));

 

 

 

the main purpose of this formula is to generate the wo options to select from, "Not Completed" and "Completed" for the Dropdown control for the main scenario that is the subject of your initial question.

 

 

Controls and other items present on Screen1:

 

One Gallery with Layout set to 'Title' on the right pane.

 

Presumes also one Data Source of SharePoint List, data source is called Completed in this example, associated with this App.

 

Gallery1 Items:

 

 

 

Completed

 

 

 

"Completed" here is referring to the specific name of the SharePoint List data source we created that was tested by us, and is not referring specifically to the name of the value of the Dropdown2 option of "Completed".

 

One Dropdown

 

Dropdown2 Items:

 

 

 

_SampleCollDef01

 

 

 

 

One TextInput

 

TextInput1 Default:

 

 

 

"Some Default Title"

 

 

 

 

One Button

 

Button1 OnSelect:

 

 

 

If(Dropdown2.Selected.Result = "Completed"
,
   Patch(
      Completed
      ,
      {Title:TextInput1.Text}
   )
,
   Navigate(Screen2)
)

 

 

 

The above checks if the dropdown value is "Completed" - if it is, performs the Patch to SharePoint List Data Source (which is actually named Completed in this case) using the Text Value present in TextInput1,
and if dropdown value is something else than "Completed" - then it will do something else - in this simple example, it will navigate to some other Screen.

 

 

 

 

On Screen 2:

 

One Label

 

Label1 Text:

 

 

 

"This screen being navigated to when Completed is not the current dropdown value."

 

 

 

 

One Button

 

Button3 OnSelect:

 

 

 

Navigate(Screen1)

 

 

 

 

 

 

Sample app and instructions to import the sample app to play with yourself: 

 

AppCompletedSample-898253-v1-coll.msapp

 

This sample app is different and does not match exactly the Explanation above. This is because this sample app does not use SharePoint List data source, but instead uses inline mock Collection -- so notice it uses Collect instead of Patch as well there - so use explanation above instead for that one with SharePoint List, and use msapp as starting point on conjunction with the explanation above. The graphic showing it working at very top of this post, in SharePoint List, uses the version tested with SharePoint List (not provided here as an msapp file attachment - only the provided Explanation above is associated with that working version we tested). The reason is so that you can play with it yourself using local mock Collection right away on import for easiest import and maximum portability.

 

In case you still do want to import the attached msapp file to play with the sample App yourself:

 

msapp import:

 

  1.  Navigate with your browser manually to this URL (or just click the following link): https://us.create.powerapps.com/studio/
  2.  Then, Click "Open" on the left side
  3.  Next, Click "Browse" on the right side
  4. Finally, select the msapp file from the window when prompted.
  5. Done

The attached msapp version  AppCompletedSample-898253-v1-coll.msapp differs slightly from the actual tested app that is subject to the graphic and full explanation above - here is a graphic of the msapp version of local collection version sample app as well in case, but notice that this app version differs slightly from the version used in Explanation and the graphic at the top (no msapp is included for version tested by us with SharePoint List - but full Explanation of all key formulas and Controls, included above. Also since the app versions are very similar, you can easily just import the attached msapp then change just a few formulas using the full Explanation above, for it to point to your specific SharePoint List and just use Explanation above to make the relevant changes).

 

AppCompletedSample-898253-b.gif

 

 

 

View solution in original post

1 REPLY 1
poweractivate
Most Valuable Professional
Most Valuable Professional

@Questionasking 

Result working:

 

AppCompletedSample-898253-a.gif

 

 

Explanation (for the explanation it was tested with a real SharePoint List and found to be working - note that this actually differs a little bit from the attached msapp file at the bottom of this post):

 

Working SharePoint List Patch Example App (not provided as an msapp in the attachment - so see instead full explanation below, and possibly import attached msapp and adjust it using the below explanation if you want):

 

App has two Screens, Screen1 and Screen2 (Screen1 is most important - Screen2 is optional but if using exactly this specific example, both screens should be there in that case):

 

On Screen 1:

 

Screen1 OnVisible:

 

 

 

 

 

Refresh(Completed);ClearCollect(_SampleCollDef01,Split("Not Completed,Completed",","));Reset(Dropdown2);Reset(TextInput1);

 

 

 

 

In the above the most important part is just:

 

 

 

ClearCollect(_SampleCollDef01,Split("Not Completed,Completed",","));

 

 

 

the main purpose of this formula is to generate the wo options to select from, "Not Completed" and "Completed" for the Dropdown control for the main scenario that is the subject of your initial question.

 

 

Controls and other items present on Screen1:

 

One Gallery with Layout set to 'Title' on the right pane.

 

Presumes also one Data Source of SharePoint List, data source is called Completed in this example, associated with this App.

 

Gallery1 Items:

 

 

 

Completed

 

 

 

"Completed" here is referring to the specific name of the SharePoint List data source we created that was tested by us, and is not referring specifically to the name of the value of the Dropdown2 option of "Completed".

 

One Dropdown

 

Dropdown2 Items:

 

 

 

_SampleCollDef01

 

 

 

 

One TextInput

 

TextInput1 Default:

 

 

 

"Some Default Title"

 

 

 

 

One Button

 

Button1 OnSelect:

 

 

 

If(Dropdown2.Selected.Result = "Completed"
,
   Patch(
      Completed
      ,
      {Title:TextInput1.Text}
   )
,
   Navigate(Screen2)
)

 

 

 

The above checks if the dropdown value is "Completed" - if it is, performs the Patch to SharePoint List Data Source (which is actually named Completed in this case) using the Text Value present in TextInput1,
and if dropdown value is something else than "Completed" - then it will do something else - in this simple example, it will navigate to some other Screen.

 

 

 

 

On Screen 2:

 

One Label

 

Label1 Text:

 

 

 

"This screen being navigated to when Completed is not the current dropdown value."

 

 

 

 

One Button

 

Button3 OnSelect:

 

 

 

Navigate(Screen1)

 

 

 

 

 

 

Sample app and instructions to import the sample app to play with yourself: 

 

AppCompletedSample-898253-v1-coll.msapp

 

This sample app is different and does not match exactly the Explanation above. This is because this sample app does not use SharePoint List data source, but instead uses inline mock Collection -- so notice it uses Collect instead of Patch as well there - so use explanation above instead for that one with SharePoint List, and use msapp as starting point on conjunction with the explanation above. The graphic showing it working at very top of this post, in SharePoint List, uses the version tested with SharePoint List (not provided here as an msapp file attachment - only the provided Explanation above is associated with that working version we tested). The reason is so that you can play with it yourself using local mock Collection right away on import for easiest import and maximum portability.

 

In case you still do want to import the attached msapp file to play with the sample App yourself:

 

msapp import:

 

  1.  Navigate with your browser manually to this URL (or just click the following link): https://us.create.powerapps.com/studio/
  2.  Then, Click "Open" on the left side
  3.  Next, Click "Browse" on the right side
  4. Finally, select the msapp file from the window when prompted.
  5. Done

The attached msapp version  AppCompletedSample-898253-v1-coll.msapp differs slightly from the actual tested app that is subject to the graphic and full explanation above - here is a graphic of the msapp version of local collection version sample app as well in case, but notice that this app version differs slightly from the version used in Explanation and the graphic at the top (no msapp is included for version tested by us with SharePoint List - but full Explanation of all key formulas and Controls, included above. Also since the app versions are very similar, you can easily just import the attached msapp then change just a few formulas using the full Explanation above, for it to point to your specific SharePoint List and just use Explanation above to make the relevant changes).

 

AppCompletedSample-898253-b.gif

 

 

 

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,213)