I created a "ticketing system" in Power Apps and created the workflow in Power Automate.
The long-story short is this -- on the "create a new ticket" screen, the Patch function is working as intended for all fields displayed (e.g. combo box user-selector, dropdowns, text input, etc.) and none of them are inside a Form. Once the user clicks the "Create my ticket" button in the app, the Patch function runs and creates the new item in the SharePoint list. Once the item is created in the SharePoint list, Power Automate gets automatically via the "When an item is created or modified" action and sends them an email with the Status of their ticket. They will receive additional emails as the Status of their ticket changes.
I followed Shane Young's video (https://www.youtube.com/watch?v=K74UFYgrKB4) about how to create an Attachments field (I know that's the wrong way to describe it!) to the Canvas app by adding an Edit Form, connecting it to the list, copying the Attachments field, pasting, then updating some settings. I did find this to be VERY informative and probably going to be one way for me to accomplish what I'm setting out to do.
The "problem" (using that loosely) is that there's 23 fields getting patched (this includes 4 admin fields and 10 fields that will appear based on the request type). Having to recreate this in Power Automate seems like a lot of work - if it was a few fields, I think it would be pretty easy.
Could someone recommend a way to Patch the attachments instead of using Power Automate? Or any other recommendations? Thanks very much!
Hi @Chris110 ,
That is going to be a lot of work, when it all could be simply done with a Form and (if you must Patch) simply Patch(FormName.Updates), You can also send the email directly from PowerApps (Office365Outlook.SendEmailV2) and really do not need a Flow for any of it.
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
Thanks for the reply.
Personally - I'm not a fan of Forms. I prefer to create my own Canvas app from scratch because I enjoy the flexibility of being able to be as creative as I want. So I'd like to avoid going down the Form path.
I'm ok with adding complex code to my patch function. And I think the system we came up with (Power Apps for intaking the ticket and Power Automate to send nicely formatted, clear emails) is working pretty well.
If you must go down that track, then you cannot Patch attachments - you will have to use Power Automate, which is a much more complex process especially if you want to do multiple attachments at the same time.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Join us for the next call on June 15, 2022 at 8am PDT.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.