I am new to power automate and following examples I found on the internet I created my first flow. The flow sends attachments added to a SharePoint list via a PowerApp application to a SharePoint document library. The problem is that the way the flow is set at this moment; attachments remain in the SharePoint list after they have been sent to the library, creating duplication of data.
I have tried adding an additional step to the flow using information I found on the internet, but no matter what I try I get the warning Actions in this flow may result in an infinite trigger loop. Please ensure you add appropriate conditional checks to prevent this flow from triggering itself.
Right now, I have the end users manually deleting the attachments from the list after they have been sent to the SharePoint document library, but this is not practical in my scenario. I want to add an additional step to the flow that automatically delete attachments in the SharePoint list after they have been sent to the SharePoint document library.
Attached are the images of how the flow is set up:
Solved! Go to Solution.
Inside of your Apply to each loop and immediately after the Update file properties, add a SharePoint Delete attachment action. Let me know if you need additional help.
Thank you so much for responding so fast! I get the same warning. Also, I am not sure which ID applies for the *Id and the *File Identifier.
Hi, I hope you are well.
I'm with the same question, but in my case it would be to delete the attachment saved in the sharepoint folder. For example I have a sharepoint list where people create items and attach documents. Attached documents are created in the item's folder. Let's suppose the person deletes a document from the list, I need that deleted document to be deleted from the folder as well.
Thank you very much for your attention and help.
Keep up to date with current events and community announcements in the Power Automate community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!