Unanswered

Power automate flow does not work when item is created through power apps

(0) Share

Report

Posted on by shelvia

Hi there,

I've created a power app form that goes to a SharePoint list successfully. I've also created a manually tested a flow that works successfully that when an item is created, a Microsoft document is populated with the form information (then converts to a PDF, Attaches to the SharePoint List, and sends an email to a project manager).

However, when I submit the form from power apps the flow is not triggered. Ive been trying to trouble shoot it but none of the basic stuff i have found works.

I would try to do it through the power app but my form has so many fields that the "Ask in PowerApps" route so incredible complicated.

Any Help would be so apprecriated!

Categories:

Building Power Apps

I have the same question (0)

All responses (18)

Answers (0)

Sort by

Anchov 1,986 on at

Like
a
(0)

Report
Copy link

Link copied!

Check the version history of the original item that is created in SharePoint. Is there just a single create event? Is your Power App immediately writing anything back to the item created right after the submit form event? I am thinking something like a Patch function that modifies the item right after the submit event, which may nullify the Create trigger before it has a chance to trigger the workflow.

Was this reply helpful? Yes No
SebS 4,867 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

@shelvia

Must be something wrong with setting up of site and List in your trigger. Other than that, I don't see why it will not trigger.

You can use the Power Apps V2 trigger, create a variable number, call it PowerAppID
then after add Get Items and in ODATA filter, add ID eq PowerAppID, and then the rest of the flow fills the world from get Items which will pick a record based on PowerAppID passed to ODATA Filter

Add this flow to Power Apps and in OnSuccess add "FlowName".Run(Form1.LastSubmit.ID) Make Sure You rename Form1 to the name of Your form and FlowName to the name of the flow You add

Hope You find out what is wrong or this work around will help You

Was this reply helpful? Yes No
shelvia 70 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for responding @SebS!

Im interested in the work around you mentioned. Can you elaborate some more on it or refer me to a resource that would?

Thanks,

Was this reply helpful? Yes No
SebS 4,867 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!
@shelvia

Sure,

Power Automate have a trigger called PowerApp v2 delete your trigger and pick it up by typing in the search it name

You can add Variables to that trigger what will be passed from Power Apps to Power Automate so in this scenario Pick Number and call it PowerAppsID as below

Now when the trigger is ready add Get Item cause you will deal with one Item at a time that will make it easier as You will be able to pass ID directly like on the screen below

Then the rest of your current flow goes from there and You use Get-Item to fill the form as it will contain all data from the last submitted record.

Save the flow and go to power apps
Left side you can see the power automate icon press it and in the window, there will be an option to add the flow
Add this flow

Now in the submit button or in OnSuccess of the form add

"FlowName".Run(Form1.LastSubmit.ID)

this code will retrieve ID of the last submitted form and Trigger the flow as an instant with the variable passed to it of the last ID what then allow Get-Item to find right record in Your SharePoint List

Hope this make seans

Was this reply helpful? Yes No
shelvia 70 on at

Like
a
(0)

Report
Copy link

Link copied!

@SebS Wow thank you for the great instructions here!

Im going to test this out tomorrow and see if this will solve my issue.

Was this reply helpful? Yes No
shelvia 70 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anchov,

You're speaking a little over my head there.
This is a screen shot of the OnSelect of my submit button if that anwers your question?

Was this reply helpful? Yes No
Anchov 1,986 on at

Like
a
(0)

Report
Copy link

Link copied!

@shelvia Looking at your screen shot, it looks like you Submit event is updating existing entries in your SharePoint list with a Patch function. This would modify an existing record and not trigger your workflow. Based on your prior screenshots, your workflow is only triggered by create event (only brand new records).
You can change your trigger action to "When and item is created or modified", and it should trigger on any save event (new or existing). Just be aware that you may need to add additional trigger filters so you don't get into a situation of an infinite looping with your workflow (the flow edits the record, and then triggers itself indefinitely without exit).

Was this reply helpful? Yes No
shelvia 70 on at

Like
a
(0)

Report
Copy link

Link copied!

@SebS Okay couple of questions.

When I Set up the trigger and select Number, what number do i enter next to it? its prompting me to have something there.

and on the Onselect of my submit button i have a form that is using a variable to go across multiple screens, it doesnt seem like I can use the variable where you have Form1 in that last string you suggested. Any ides on how i should modify the Submit Button? (below is what i currently have on the OnSelect

Was this reply helpful? Yes No
shelvia 70 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anchov Very interesting!

Is there any measures I can take to prevent the infinite loop? I came up as a warning when I was trying to test this out

Was this reply helpful? Yes No
Anchov 1,986 on at

Like
a
(1)

Report
Copy link

Link copied!
Yes, you can add Trigger conditions (or filters) to your initial trigger. Here is an example.
Good article with more examples:
https://www.spguides.com/power-automate-trigger-conditions/

Basically, the trigger conditions adds additional logic in your trigger listener that tell it only to fire when certain conditions are met. For example, in the screenshot above, only when the SharePoint list item has attachments and the Attachment URL is null. Later on in the flow, I am updating the SharePoint item with a URL text values, so when the item is updated, the trigger doesn't fire again.

Two things to note:
The warning you see will not go away, even when adding trigger conditions. It is just letting you know that an infinite event could occur, not that it will.
If your flow is not writing back (updating) to the current SharePoint item that triggered the workflow, you should not have to worry about this. I can not tell from your screen shot.

Was this reply helpful? Yes No