Jul 27 2020 08:12 AM
Jul 27 2020 08:12 AM
I have a Microsoft Form set up where I am requesting a first name, last name, email address and an ID value which is a number for an event I am holding. Only authorized members can attend this meeting, and I authenticate this via the ID value that's captured and look it up according to an Excel spreadsheet I have stored in OneDrive for Business.
I want to use Power Automate to do the automatic authentication by taking the ID value from a Form submission, match it to the values in a table in an Excel spreadsheet stored in OneDrive for Business. If the ID matches, Power Automate must send an email to the recipient providing details to the meeting, i.e. the meeting link. If the ID does not match or is not found, the recipient gets an email stating what's the next procedure (a manual verification step - not created in Power Automate). The ID is a numeric value. It's captured as a numeric value on the form. The table has the IDs stored, formatted as "General".
I added the following steps:
When I test the flow, I get an error at the "List rows present in a table" step. Under "Inputs", I can see the ID value captured under the "Filter Query" field. Under "Outputs", an error is shown. The error is reproduced below:
Status Code: 400
Mon, 27 Jul 2020 14:36:37 GMT...
Jul 28 2020 11:37 PM
Have you tried removing the filter from List rows present in a table?
Your condition already matches the ID from the form response to the ID listed in your spreadsheet so the filter is not needed.
Let us know how you go?
Jul 29 2020 07:39 AM
Thank you for responding.
When I remove that filter from List rows present in a table , the Apply to Each control goes into an infinite loop where I get bombarded with infinite emails from the If no condition. I had to stop the flow and disable it else it would have been catastrophic.
Jul 30 2020 01:18 AM
If it gives you the right result but continues in an infinite loop, try a Terminate action (set it to Succeeded) after the Send email action.
That'll kill the workflow after the first execution which should give you the desired email outcome and also stop getting spammed.
There's other ways to get around this, but this is the first thing that popped into my head that's easy to implement.
May 03 2021 05:57 PM