Hello,
My personal environment was closed and I was not able to restore it, but I could back up the applications into a solution pack. If I open this solution pack file with .osp extension, it requires a password, and I didn't cofigure that previously, so I don't know it, it's not my OutSystems login password:
But I discovered that if I rename the solution pack to .zip extension, it shows all backed up applications as .oml files.
If I install each .oml in the new environment it becomes an independent module in a folder of same name.
How can I install each .oml file or the solution pack to the new environment as applications instead of independet modules?
Also, I noticed some .oml files from the solution pack seem to be already installed in the new environment, such as SingleSignOnMobile, and I don't want the old enviroment modules/apps to overwrite the ones of the new enviroment.
What should I do in this case?
These are not errors, but warnings. Once the installation is complete, open your application, refresh the dependencies, and verify that everything is working as expected.
Hello @Elisa Amaral,
Yes, as Siya mentioned those are warning not errors, and if we see those warnings it is because of missing dependencies, that application dependent application was not there.
So as mentioned siya, you have to refres dependencies once installation done and see if there are any warning appear again, if again any warnings came, then please read that warning and understand which application it is missing and search weathering it is installed or not if not please install and refresh again.
Prabhu K
First of all logon to the Service Center of the new environment. Then go to Factory-> Solutions -> Upload & Publish a Solution and upload your OSP file here. It will take a while to restore the file and will work.
Yes, as mentioned siya, you have to logon service center, upload and publish solution( Service Center > Factory > Solution > Upload and Publish Solution), here as you mentioned already existing applications will move to independent module in a folder of same name, so later you can remove those.
Otherwise, you need to publish individual selected modules over Service Center > Factory > Modules >Upload and Publish Modules by not considering existing applications.
And another not recommended approach is that you need to Remove existing applications over Environment and publish your solution so that Applications won't move to independent modules folder and advantage here is you can get same compatible dependent applications also, then you no need to fix any dependencies.
Regards,
@Siya @Prabhu K thank you for your help.
I installed the .osp in Factory>Solutions, now Service Center is waiting for my response to finish the update (Continue/Abort Publish), as some errors showed up along the installation. Here are part of the errors:
It's odd because all applications being restored are exercises from the OutSystems Learning guided paths. So why so many errors? Some applications have already been installed in Service Studio, but I'm not sure if they're updated to the latest changes I did before the previous environment was shut down.
I wonder if the best option isn't re-doing all the exercises from scratch instead of restoring the backed up ones, though that would take much more time.
What could I do?