Remove the alert notification for the internal/temp file "VerifyPerm(GUID)" from being sent when alerts exist & document moved between libs.
Remove the alert notification for the internal/temp file "VerifyPerm(GUID)" from being sent when alerts exist in both document libraries (source and destination) and you use the ribbon "move to" feature.
Two emails are generated as expected, one for the file getting created in destination, and one for it getting deleted in source. However the issue occurs once this is done, a second email will be sent out with the title: "VerifyPerm(GUID)" for a temporary (non exposed) file which gets generated to check the permissions in the destination location. This is unesesary. Please remove this secondary message.
I have the same problem, when I copy or move a file from one library to another using P.A. flow, VerifyPerm([GUID]) was created. Is there any solution to stop this kind of file to be created?
Same issue here: a sharepoint location is being created automatically for each dynamics Account record that is created. A flow then copies over a default template to that newly created sharepoint location. For some accounts, the root of the sharepoint location contains this (empty) VerifyPerm(GUID) file, and it seems to be causing some problems with deleting/adding new files in that directory...
Alex Hicks commented
Getting this bug when using PA Flow + SharePoint copy file action. File is copied and then a second file is created with the name "VerifyPerm([GUID])".
Is there any solutions about this case. I search it but can't reach any viable document about it.
Yet another bug in SharePoint / Flow
Jake Jeffries commented
Has there been any updates to this? I've been receiving emails like this for the past few days
Chris Ball commented
I too am experiencing the same but in the 'Copy To' extension when creating copy files from Onedrive to SharePoint. Found it was OK to delete, but agree with the poster, Bret Ustipak, that the second is unnecessary and therefore request Microsoft to remove the secondary message.
my flow that moves items into a folder apparently left this file behind. I had to google it - i found no documentation that this would show up. glad I found it before the client did - is it ok to delete it??
Interesting. I just ran into a similar issue with the VeryPerm(GUID) files not being deleted and prevent further actions on items in the same location.