Update User Mapping in PowerShell
2
votes
James
shared this idea
-
Tony Marolla
commented
My colleague brought this to your attention and this is not an "improvement" but a bug in your Powershell. The fix is to get the import user mapping process to work with a CSV file that contains usernames from both the Source and Target. AvePoint is able to pull it in by CSV file. To be competitive, this should be fixed.