So basically I have a flow which accesses a "submitted file" which is an excel file which is just a filled in template that the user dumps into a submit folder which exists on a SharePoint. The data within the table in the submit file is then read line by line and then a composite key is constructed within the flow and then finds the relevant row within the result master file (the main database of the whole process), and depending on whether it exists or not within the result master file, it will add or update the relevant row.
I have asked about using SharePoint lists instead, the user is adamant about using excel to store the data.
I've already constructed the solution to this, but one thing which is more so an issue for keeping things organized is that the submit folder just gets messy.
So I have another flow which organizes an archive folder. The only issue I have is that the I want to move the submit file after the main process has been completed. I've tried using move file but it throws an error because the flow apparently has that file open and thus can't move it.
I've got a work around where I have a parallel branch of the original flow which copies the file to the archive folder, so that is being sorted automatically, but I would love for the original file to be moved instead of copied as then it will keep the original metadata such as created by. Also my work around doesn't have the ability to delete the file automatically in the submit folder so there is still the issue of the folder looking messy.
Is there a way to purposely close the flow's access to the file so it no longer affects the "move file" block in the flow?