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. 😂
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.
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?
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.
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?
Thank you for another great video, Paul! I can't wait to attend your session at the Nordic Summit.
Look forward to meeting you!
As always "Short 'n Sweet" 🤩
I try to keep them short, but wonder if I am going too fast at times. Thank you 😊
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. 😂
This was an incredible video that helped me out with a huge project at work. Much appreciated!
That’s great news Halle, glad it helped you out. It is a neat solution.
Great video. Thanks
Thank you sir!
You are welcome!
Very good video. Thanks a lot
You're welcome. What are you using it for?
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.
Yes, you should be able to, what is the issue you are having passing the email address around?
@@PaulieM I have figured it out. Thanks so much for your response.
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?
It is not because you do not have premium. Have you checked in the old version of the designer?
@@PaulieM I am using the old designer. I am not a fan of the new designer 😆
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!
Brilliant- well done. Hope your flow worked out well. 🤖 💪🏻
This is a great video, thanks for putting it together! What about having a text input besides the buttons? do you think that is possible?
It’s not possible in the email itself, but you could link the email to a form which accepts text input.
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?
I’m not sure, happy to help you out if you use the get in touch form on my blog.
@@PaulieM Thanks, I will. :)
Instead of using guid(), can you use the ID column when the item is created? Or that is not available when the flow is triggered?
You can use the ID. It just opens up the URL to easy manipulation.
wow thank you sir
Glad you found it useful.
Great Work,
Is there a way to run a Flow without opening a new page?
Not with a HTML button like this, but you can do it with an adaptive card.
Great work, Paul.. but why not use the "send email with options"-action. That one is not premium
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.
Also, you can customise your response to the client - and perhaps collect even more information from them by leading them to a form.
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.
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?
I don’t think it is. You could build a page with graph toolkit that runs under the context of the logged in user.
Cheese and beetroot?!? I'm ordering pizza.
Will join you. You’re gonna have beetroot on a pizza? Sounds crazy but it could work!
@@PaulieM 🤮 Proud to say I've never had a beet or a beetroot. But you do you.