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

Do not require attachments if condition met

Hello, 

 

I have an already existing flow when a form is submitted to run the flow for approval. It requires attachments for each submission. However, there is a question named "Emergency" which if selected i would like the attachment to not be required and still trigger my flow to run. Currently it will fail at the supporting documents step.

ElvirBotic_0-1702402805674.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
eliotcole
Super User
Super User

Hi, @ElvirBotic, I'm going to assume that 'SupportingDocuements' is either a Filter or Select data action ... but it's not entirely clear, since all we can see here is the symbol.

 

Could you expand that step and a few of the related steps around it, then update your question with the images, please?

 

Purely running on the assumption above, I would say that you could run one of two options, the first of which may not be possible:

  1. Trigger Conditions - Duplicate the flow and place trigger conditions in both:
    • This Flow - Ensure that there ARE attachments
    • New Flow - Ensure there are NO attachments
  2. Add Logic To This Flow - Just do a little more 'logicking' in this flow

 

 

Trigger Conditions

I'm not going to get massively in to this, because there are plenty of guides, however if there is the ability within the trigger to know whether the form entry had attachments, then you could ensure that there is a flow to handle either eventuality.

 

Additional Logic

Below is a few steps that might help you better lay out your flow to have more of an idea of where and how things are failing. It may even mitigate that entirely, I hope! ...

  1. Initialize 3 Variable Branches - Add 3 parallel branches to initialise variables at the start of the flow

    If you don't have that many variables just place holding actions (Compose or empty variables) in them
     
  2. SupportingDocumentsArrVAR - Ensure one of the variables above is an array variable type with this name and refer to this where you would have referred to your existing SupportingDocuments action
     
    Oh and initialise it with the value:
    []
     
  3. Scope VariableProcessing - Make a Scope which joins the 3 branches and name it this and inside the scope you can process setting these variables
    • Condition DecideSupportingDocuments - Make a Condition action named this which reacts to whether or there are documents attached
      • Yes - ... there are documents - ... use the current action to Set SupportingDocumentsArrVAR
      • No - ... there's no documents - ... no wuckas nothing to do here

 

Now your flow should have an empty array of SupportingDocuments if there are none and a full one if there are any.

 

---

 

Why Variable Branches?

The reason that I was a little prescriptive with you about laying out three parallel branches for the variables at the start is because it is just a really good practice to get in to.

 

Especially so when you make the action which joins them a Scope which you use to process as many of them as possible, as above. 🙂

 

What this will hopefully lead you to in the future is failure / error handling within your flow. Because you can then run a different set of actions if the variable processing scope fails for any reason ... or indeed any Scope containing actions.

View solution in original post

2 REPLIES 2
eliotcole
Super User
Super User

Hi, @ElvirBotic, I'm going to assume that 'SupportingDocuements' is either a Filter or Select data action ... but it's not entirely clear, since all we can see here is the symbol.

 

Could you expand that step and a few of the related steps around it, then update your question with the images, please?

 

Purely running on the assumption above, I would say that you could run one of two options, the first of which may not be possible:

  1. Trigger Conditions - Duplicate the flow and place trigger conditions in both:
    • This Flow - Ensure that there ARE attachments
    • New Flow - Ensure there are NO attachments
  2. Add Logic To This Flow - Just do a little more 'logicking' in this flow

 

 

Trigger Conditions

I'm not going to get massively in to this, because there are plenty of guides, however if there is the ability within the trigger to know whether the form entry had attachments, then you could ensure that there is a flow to handle either eventuality.

 

Additional Logic

Below is a few steps that might help you better lay out your flow to have more of an idea of where and how things are failing. It may even mitigate that entirely, I hope! ...

  1. Initialize 3 Variable Branches - Add 3 parallel branches to initialise variables at the start of the flow

    If you don't have that many variables just place holding actions (Compose or empty variables) in them
     
  2. SupportingDocumentsArrVAR - Ensure one of the variables above is an array variable type with this name and refer to this where you would have referred to your existing SupportingDocuments action
     
    Oh and initialise it with the value:
    []
     
  3. Scope VariableProcessing - Make a Scope which joins the 3 branches and name it this and inside the scope you can process setting these variables
    • Condition DecideSupportingDocuments - Make a Condition action named this which reacts to whether or there are documents attached
      • Yes - ... there are documents - ... use the current action to Set SupportingDocumentsArrVAR
      • No - ... there's no documents - ... no wuckas nothing to do here

 

Now your flow should have an empty array of SupportingDocuments if there are none and a full one if there are any.

 

---

 

Why Variable Branches?

The reason that I was a little prescriptive with you about laying out three parallel branches for the variables at the start is because it is just a really good practice to get in to.

 

Especially so when you make the action which joins them a Scope which you use to process as many of them as possible, as above. 🙂

 

What this will hopefully lead you to in the future is failure / error handling within your flow. Because you can then run a different set of actions if the variable processing scope fails for any reason ... or indeed any Scope containing actions.

Yes, I see. I appreciate the information. I explored triggers as an option. I think I will go that route and just validate if there are attachments or not for non-emergency submissions vs emergency submissions. Then I will just have another flow for Emergency submissions.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,113)