Import Application Failure

[mitchellhenry]

Using Helsinki in my DEV instance, I'm trying to import an application from source control, and receiving the following error:

"The application has been changed since it was last imported or exported. Either export the changes or elect to lose unsaved work."

This is my first import (the application didn't previously exist in my instance).   I've tried both BitBucket and GitHub...same error.   Also, I've made no changes directly on the data outside of ServiceNow.

Any help will be greatly appreciated!

-Mitch

[hmh]

Hi guys,

I'm having the same problem. (Same error message as the screen shot above). And system logs show the following error - sys_repo_config record does not exist by sys_id: (long sys_id here)

I'm trying to import an application which does not exist on the instance before. It was installed as an app before though on that instance but we have uninstalled the app.

I would really appreciate any pointers how to solve this problem.

Thanks,
Hsu

[Ben Vargas]

Did you ever get this figured out hmh and mitchellhenry? I am having a similar problem where I needed to change the github repository name/URL and I took the following steps

01. Deleted Application (it was originally created on the same instance and pushed to github).

02. Deleted the sys_repo_config record and it prompted to delete a few stashes related to the repo.

03. Attempted to use Studio to import the application again, from the fixed repository address/name.

RESULT: Error received, same as Mitch's screenshot and similar error in the system logs.

The above steps worked perfectly fine from a developer instance I was using to do some side POC development on the application, but the original instance that created and committed the app to the repository fails with the same error you note and pictured by Mitch Henry.

[Ben Vargas]

In some additional testing, I found the import from source control to fail with the same error in any instance registered to the customer. A POC instance that had never had the application on it failed with the exact same error, so I somewhat suspect that import from source control is failing to create the new application because the scope name has already been used for the original application that was since deleted - and it's registering somewhere on the ServiceNow side (my only explanation for a customer's POC system failing that never had the application on it to begin with).

To recover I loaded an XML copy of the application created using "Publish to Update Set" prior to deleting the original application; that worked and the application was back on the instance it was originally created on. I then linked it to a new github repository which worked fine and commits are good.

However, if I on the POC instance I go to studio and retrieve from source control from the same repository dev1 is using, the error persists. Using a different developer instance the same import from source control works fine... reaffirming that it may be related to the application scope registering somewhere for the customer and thus failing whereas developer instances load fine.

I've gone ahead and opened a HI ticket to investigate further... to be continued.

[John Caruso]

Not sure if Mitchell is getting notifications, so benvargas, I'll pose the same question to you:

Just wondering if this remains unresolved. There is a fix in Helsinki Patch 3 that appears to be related. Have you applied that yet? I'm running into this same issue and want to confirm the patch fixes it before applying.

Thanks,

John

[Ben Vargas]

It actually "resolved itself" working with the client's instances... I had replicated it on the phone/webex with support, but by the time it was escalated to a new support group it began working. I thought that they may have made a SN-side change with scoped application naming and these imports from GitHub, but the support rep didn't have any info on that. I had to move on and accepted the solution as working... my client has cloned from Prod a few times and it continues to work.

At the time the client was in the process of patching to 3, but the POC instance it suddenly began working on had not yet been patched (though the dev instance it was created on had been). It's possible that patch 3 helped resolve it. My first step would be to get on Helsinki Patch 3 or later, and then if still not working I would open an Incident with support.

Clear as mud 😕