"When an item or a file is modified" triggers when new list item is created

[tagustin2020]

Hello,

I am in the process of building a Shipping Request app. I have three flows for the app. One that runs when a new item is created, one that triggers "When an item or a file is modified" for situations where the requestor needs to edit their request and one that fires when the status of an item is equal to Shipped. The problem is that when I submit a new request, the "when an item..." flow fires as well. I already set up one condition to make sure it doesn't fire when the shipment notification is sent, but I'm not sure how to write an expression that prevents it from firing when a new item is created. Can you help me out? I don't currently have any special trigger conditions set up in the ...Settings next to the trigger or "Get changes" step. Thank you, Teresa

[ScottShearer]

@tagustin2020 

The When an item or file is modified trigger should not be firing when the item is created.  

How is data being entered into the list?  Is it possible that a save is occurring more than once?

[tagustin2020]

@ScottShearer 

Hi Scott,

Thanks for responding to this ticket. The app is essentially done, minus this flow glitch. I demoed the app to the Logistics Team today and they really like it (hooray!), but I don't want to grant them permissions to beta test the app until this issue is resolved. My app is a multi-screen app. Would setting "Defaults" on the New Request button and "Patch" on the Copy Icon be causing a "double save" effect? I'm trying to learn these tools so I appreciate your advice.

New Request Button OnSelect:

Set(varRecord, Defaults('Domestic Shipping Requests'));ResetForm(frmMasterNew);Navigate(RequestorScreen,ScreenTransition.None);

The Item property of the Requestor, Recipient and Details Forms is: varRecord. The OnSuccess of each is: false.

The Item property of the Master Form that actually submits the updates to the SharePoint site is: 

Patch(varRecord, frmRequestor.Updates,frmRecipient.Updates,frmDetails.Updates)

The OnSuccess property of the Master Form is:

Patch(
    FormPageStatus,
    {Page: CurrentPage.Page},
    {Status: "Complete"}
);
UpdateIf(
    'Domestic Shipping Requests',
    ID = Self.LastSubmit.ID,
    {'Request Number': Self.LastSubmit.ID + 10000}
);
UpdateIf(
    'Domestic Shipping Requests',
    ID = Self.LastSubmit.ID,
    {DocVersion: Self.LastSubmit.Clicks + 1}
);
Set(
    HighlightRecord,
    frmMasterNew.LastSubmit
);
Navigate(
    HomeScreen,
    ScreenTransition.None
);
Set(
    varPlaySpinner,
    false
)

As I mentioned earlier, I also have a copy icon in my app. The OnSelect formula for the copy icon is:

Set(varRecord,Patch(LookUp('Domestic Shipping Requests',ID=ThisItem.ID),{ID:Blank()}));Navigate(RequestorScreen,ScreenTransition.None)

All the other form formulas for when a user is making a copy are the same. The Modified trigger fires when a copy of a record is submitted.

If the OnSelect and/or OnSuccess formulas are the culprits, I'd be grateful if you can think of some kind of conditional logic I could apply either in the app or in the flow to make it recognize new versus edit "modes".

Thank you,

Teresa

[tagustin2020 · Accepted solution]

@ScottShearer 

Hello Scott,

I was able to figure this out over the weekend. For the sake of anyone else reading this post, here is how I solved the misfire outlined in the problem statement. The Default status of my Status Choice column is "New" so I added another Status called "Revised" and added a Patch statement to the OnSuccess formula of my Edit Screen form. The Visible property of the Status data card in the edit form is set to false since this formula automatically sets the revised status when the Requestor makes a change.

Patch(
    'Domestic Shipping Requests',
    {ID: Self.LastSubmit.ID},
    {Status: {Value: "Revised"}}
);

I then went into my flow and added a condition after the Get changes step to indicate that the flow should only continue to run if the Status is not equal to New or Shipped (I have a separate flow for shipment notifications). I submitted a new item to test this and also edited an existing item and both flows, the one that fires when a new item is created and this one, seem to be working as desired now. 

[radosopon]

Just to add a little more insight on this firing topic, this trigger react on the situation, when item is created with attachment(s). It works then like this: Event Create (storing list item metadata) - trigger does not react followed by Event Modify (storing the attachment) - trigger fires. You can see this if you check list item version history. And on top of that - if you attach more files, it fires so many update events, how many files you have. This is really bug Microsoft should fix.

[JOVAZ]

In addition to @radosopon comment one way to avoid this is to turn off "Create a version each time you edit an item in this list?" in share point >>list settings>>version settings. My item was solved with that, both power automate flow running as spectated, I got the same issue from @tagustin2020 .

[mak123]

I am patching from a power apps a new status into a sharepoint list. 

On the power automate though, "When an item item or file is modified" it stays loading. Any suggestions on how to work around it?

[tagustin2020]

@mak123 

Hello mak,

I suggest you start a new post for this question and include your Power Apps Patch formula. 

Kind regards,

Teresa