Web - upload an app - disabled
Answered
I'm trying to understand whether I can use the "upload an app" functionality in the Web designer to load a previously saved app from a different portal environment (i.e. json and xml file).
I created an app in our Development portal environment, then deployed it to our UAT portal environment. It worked great, but I cannot access it when launching the UAT-based web designer. Since this doesn't seem to be a bug, I thought I could possibly download the UAT-based app from the dev instance of designer, then upload in in the uat instance of the designer. Unfortunately, the designer doesn't seem to support the ability to upload an app from scratch.
Overall, I'm trying to figure out what the download/upload capabilities do and how I can leverage it. One of the concerns we have is whether we can recreate a web solution in a different portal environment if we need to alter the original one.
-
Hi Mike - A few hints that might help.
First, you are correct, Designer is setup so that only 'dev' apps can be opened and modified. So the app that was deployed to your UAT portal environment (test/staging app) couldn't be opened in Designer.
Second, when we upload an app, we need somewhere to put the content so we do require an app to be saved first. The most common flow is to open a blank app and save it. In some cases there are resources that need to be handled, and those need a portal item which is why you have to save something before you can upload an app.
To 'move' something from one portal to another you can do it manually or use the deployment features.
Manually you'd export the dev app on portal A, then on portal B create and save a blank app and then upload the .zip you downloaded on portal A and save it.
Deployment features, you'd configure your deployment pipeline so that when you deploy the app it goes to a different portal.
1
Please sign in to leave a comment.
Comments
1 comment