Scoped Application Issues After Cloning on Development Instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2023 02:00 PM
Hi All. I am looking for a simpler solution than some of the documentation/forum postings that I've found.
Scenario:
I have a scoped application in which I created in our Dev. instance & linked/committed it to source control (BitBucket Git Repository) prior to our most recent cloning over our Dev/QA instances with the Production image. There were two versions (1.0.0 & 2.0.0) of which I'd published the application to "My Company Applications" and installed the newer version only on Dev/QA (not Production as it was still at version 1.0.0 prior to the clone).
Since the clone, the Dev instance had version 1.0.0 showing, so I attempted to use the "upgrade" option in the "My Company Applications" & it appeared as if some changes occurred, but it wasn't like it was prior to the clone in Dev. I then decided to attempt to use the "Apply Remote Changes" option in Dev while in Studio, and it found some changes; but still not where it was.
I still have the repository in BitBucket, but I don't know the best method to go about getting it where it was prior unless I ask to have Dev restored from backup before the clone. Even then, I would like to know the best process to go about doing so.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2023 02:57 PM - edited 04-13-2023 03:32 PM
Unfortunately, all I have is a link to documentation:
Seems you can retrieve the latest version from the Source control repository.
Or follow:
in the future to avoid the problem you have.