-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when running Migrate-Packages.bat #51
Comments
Can you download this latest version, please? https://github.com/Zerg00s/FlowPowerAppsMigrator/releases/download/3.8.5/FlowPowerAppsMigrator.zip I just tried it and it seems to be working. |
Thanks @Zerg00s . I was able to get past that error. Sorry forgot to come and update this issue. I do have one more question regarding the usage of the PowerShell. I am trying to migrate my custom forms from a Commerical tenant to a GCC High tenant. Do you know if this will work for a GCC High. I can connect to the source without a problem but when it tries to connect to the GCC High site is when i am unable to login. |
Hi @Chris23622131, Can you run this experiment please, to pinpoint the issue?
Let me know if that works and if not - what the error message is? |
Hi @Zerg00s there is no error message just a blank screen pops up when trying to login. I also tried this as the connection.
This is the error i get.
|
Hi @Chris23622131 , I've just created a quick Wiki page on a few things to try. Can you have a look at this, please? https://github.com/Zerg00s/FlowPowerAppsMigrator/wiki/How-to-deal-with-the-%22Make-sure-you-have-FULL-CONTROL-at-the-source-site%22-Issue If you are the lucky one who has SharePoint Tenant Admin role, then you can create a SharePoint-only app and use it for authentication. |
Hi @Zerg00s , |
This is the first time i am trying this tool. As soon as i run the bat file I get this error.
Get-FormItemProperties : The term 'Get-FormItemProperties' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
The text was updated successfully, but these errors were encountered: