Replies: 1 comment
-
I did add the following in an attempt to ensure the $upload variable was cleared after each run.
But alas, somewhere in the run, I received this error: I/O error occurred. Exception setting "UniqueId": "Cannot convert null to type "System.Guid"." Exception setting "UniqueId": "Cannot convert null to type "System.Guid"." Exception setting "UniqueId": "Cannot convert null to type "System.Guid"." No idea why nulling out the $upload object as a whole would result in this happening randomly... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have what I think is some pretty simple code which reads a CSV file consisting of about ~16,000 files. In a typical foreach loop, I make a call to Add-PnPFile like this:
From here I immediately check $upload.UniqueId as I understand if the file is not uploaded, this property will be NULL....
The issue I am having is out of these ~16,000 files, 2 of them are not actually uploaded to SPO, however, according to this code above and the corresponding log file, they are logged as successfully uploaded.
Has anyone run across this scenario and/or is there just generally a 100% reliable way to determine if the file in question was TRULY uploaded or not?
Thanks,
-jb
@VesaJuvonen
Beta Was this translation helpful? Give feedback.
All reactions