Retrieve latest version of scoped application from repository into dev post clone

[Emma Angarita]

Hi all, I'm having some trouble reinstalling the latest version of a custom scoped application into dev post clone. Here's the scenario: 

- scoped application was created in dev, published to the application repository and installed in production (version #21)

- we planned to do a clone of dev, so before the clone, I published the latest version of the application to the repository (following these steps as a guide https://docs.servicenow.com/en-US/bundle/tokyo-application-development/page/build/applications/task/...) 

- we then cloned our prod instance over the dev instance 

- the dev instance now shows the application version as per prod (expected) which is version #21

- I now want to install the latest version #23 back into dev so I can continue working on it

The application is definitely available in the application repository as the latest version (#23) is able to be installed into prod, but how do I get this version into dev?  

A few other notes - we do not use a source control repository like GitLab etc. Most of the articles I read said I needed to be linked to a source control to import the changes, but we don't and never have done this, we just use the application repository. I have also taken an XML export of the application via update set, so I have not lost anything, I would just prefer not to use this method as I'm not sure what the impacts would be and am hoping I can somehow reinstall the latest version to dev, as it appears available in prod. 

Thank you

 

[Emma Angarita]

Hello, I ended up reimporting the app as an update set, but you would have had to take an export first for that to be an option. This worked fine at the time, but I am not convinced this is a good approach as we've been experiencing issues with any further updates related to that app since doing that. It is a very old and complex app though, so may be unrelated to the export/import. Hope that helps 🙂

[Dan Covic2]

This is why it is recommended to use source control repository like GitHub or GitLab. A lot of frustrations can be avoided just by deploying your custom app onto a source control repository.

[Teresa8]

I know this is old, but I found a fairly recent KB article explaining the steps to resolve this. I had the same issue after cloning yesterday and this solution worked for me.  https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1783408