Thanks Paul for providing alternate ways to do things. It really helps us learn the concepts and understand when to make the right implementation choices. Not to mention, always great seeing Microsoft MVPs sparring inspiration off each other. And of course, the use of beetroot as a choice mandates a like.
I think I would have gone for Cheese and Beetroot also. The moisture provides much needed refreshment against the Cheese which can often be quite dry. Especially on thick bread. 😂
Hello Paul! I just discovered your page and I love your content! Question, when selecting "When a HTTP request is received" when building the first flow, when entering the relative path /(guid)/{OrderChoice}, and creating the compose step, the dynamic content does not display "guid", but it displays the other dynamic content options including the Order Choice option that I entered. Am I doing anything wrong? Or is it likely because I don't have access to the premium feature?
Then I am not sure, feel free to get in touch via linkedin or my blog and I will take a look with you. I am waiting to find someone that is a fan of the new designer. 😲
@@PaulieM I figured it out. It is because when I heard the instructions on how to enter the relative path, it sounded like I should only applied the curly brackets around the "order choice" and not the "guid". I had to zoom in to your screen to see it has a curly bracket around both. Now I see guid in the dynamic content!
Hi Paul! I hope you can help me. I'm running a similar flow to what you have here, with the differences being that my primary flow is triggered by a Microsoft Forms submission which then creates a SharePoint item and sends out an email with a call-to-action button, and the response flow updates that list item and sends out another email to a supervisor. It's mostly working right now but instead of the HTTP request trigger waiting for the button to be clicked, it triggers as soon as the email goes out. Do you know where I could've gone wrong?
Thank so much Paul, please I have a question. Can this be used to update multiple SharePoint list Statuses by different team members/users. I am having issues passing the email address of the user that triggers the flow from the email to the Http request trigger.
This would definitely get me a promotion :D Great work! well explained. Thank you so much for this video. I have not worked extensively with the HTTP Requests in Power Automate. I am planning a solution that will require me to present a form with 2 text entries (One number type and another multiple lines of text) and a submit button to the end user (Instead of 1 button for each Choice) in automated email triggered from a PowerApp. I want to ensure that HTTP link embedded in the Submit button is only valid for the person the email is intended to. i.e., if they forward the email externally or internally to anyone, the other person will not be able to enter anything in that form. Is something like that possible?
It's a really good point! I don't think I have ever used that action. I suspected that it would not work with external users, but I just tested it, and it does.
There is one disadvantage to that action. It only allows for one response, so if you were sending to many users then they could not all respond on the same email. Once the link has been clicked it comes up with the message: The workflow is not in 'Running' state. It was completed or cancelled.
Hi Paul, thank you very much for the video! Would there be any workaround to extract also the details of the user who actually submitted the response? This is a limitation of the standard email with choices,too.
