This is a strange issue. I have a SharePoint list that has been customized with PowerApps. Versioning is turned on and a Flow is running when item is modified. The flow specifically compares versions to see if the Status field has changed. The issue is that in the PowerApp when the user attaches a document on modify, it's causing an extra version to exist. This causes the Flow not to run since it thinks the status is the same as previous version. I have recreated this issue. Is there a way to remove this phantom version? I've attached a couple of the version history. Version 3 (created version 4) is when the status changed to Completed and attachment was included. Version 5 and 6 change status, no attachments.
Did you find any solution with your case? Because i have the same issue with this phantom version of the attachment without capturing the previous one from the trigger when a new item is created or modified.
No I never did. The users who have the issue have a workaround: they edit the item and add the attachment, save it, then go back in and update the status so the Flow will run. It's definitely not ideal and still looking for a solution.
In my case, i found a solution with this phantom version with attachment. In your scenario, instead of checking the status value for the flow to be triggered, try to check the versions of the attachments with a parse json action. So if the versions are equal no attachments added, if not equal (means +attachments) then check the status value and if is completed, trigger the email action.
My problems with this extra action are solved now...
Hello @Mpap could you give more info on this solution pls.
Do I need call on HTTP request
Hi all !
I am also interested and impacted by this issue.
I have a Powerapps that allow to edit a SharePoint List with a rather complexe content type, and the attachments are used.
I have also Power Automates that are triggered on items creation/modification with their dedicated logic depending on what has been modified.
What I can tell from my experience, is that :
- editing an item creates a new version
- both editing an item and adding an attachments before patching creates 2 versions
- both editing an item and adding 2 attachments before patching creates 3 versions
I guess that somehow, the item fields are saved immediately, and that the attachments creates each another version as soon as they are uploaded, seconds later.
In sharepoint Item history, there is nothing displayed for attachements updates, nor in Power Automate Sharepoint get item modification Bloc.
I can just see there are one new version with fields modifications, and one or several "empty" new version just after, with the same user.
The big issue there, is that the version are created within seconds, and that the Power Automates Item created or modified trigger checks for updates probably every minutes or so.
Then, when we analyse last modification, we just see an empty version, and the real update that happenned seconds before the last version is not processed.
I haven't found a way to deal with this behavior yet, any idea welcome !
But the worse is that dealing with this issue, I noticed other cases where 2 versions where created from PowerApps, but this time the item had no attachments.
This means that there is at least one other scenario where a Powerapps Patch creates 2 versions of the item in the SharePoint list.
Any PowerApps Pro to give his idea on the topic ?
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.