Edit 2022-06-11: Ok. I decided to give it a try and I think I managed to fix all the issues. There were several chages to column order and also data format, and I also had to downgrade my develpment environment a bit. More about that in the expandable section below.
New version of the script is added to the opening message of this thread.
[hide]
The fix itself is quite trivial. Problem is that I had developed a bunch of automated tests for my module using Pester v4.x because I was learning Pester at the time. Pester has since updated to version v5.x which was breaking change and thus broke all my tests. So, in order to fix this minor issue, I should first redo 23 files worth of Pester tests from scratch before I could start working with the actual issue. That’s because I used (and still do in my day job!) “one file per function” workflow and compile individual .ps1 files into final PowerShell module using self-made compilation script, which doesn’t actually rely on file names at all. Instead it reads function names from .ps1 file content using PowerShell’s built-in language parser. One step of the build process is testing but currently build fails because all tests are broken.
I really want to fix all that because some day I should learn that Pester 5 syntax as well, but I just don’t have time at the moment. I you want to try and fix your copy of the script by yourself, without diving into this unit testing stuff, then you could try to change lines 881 and 1138 of the WazeDataArchive.psm1 file from$dateformat = 'yyyy-MM-dd HH:mm:ss'to$dateformat = "yyyy'-'MM'-'dd' 'HH':'mm':'ss' GMT'"Meaning same change to both lines. There is couple of more instances of $dateformat around lines 22 and 167 but they should remain intact.
Then change line 1029 from$type, $dst, $displayname = $item.Split(',')to$dst, $displayname, $type = $item.Split(',')
And finally, change numbers in lines 1175 and 1177 from 19 to 23 and 20 to 24, respectively.
Actual line numbers may differ a bit because I can’t remember which version of the script is currently published. Just make sure you are editing functions ConvertFrom-WDADriveSummary, ConvertFrom-WDAFavorites and ConvertFrom-WDALocationDetails. If this doesn’t help then there must be some other change in the data I have missed.
[/hide]