Application Migration

[arunrnair]

Dear All

I am using Service Now Fuji. I have created an application in one development instance called Domain migration Pack. In another instance i have created 2 domains. To import an application from one domain to another, the Domain name and domain sys_id of the source domain is replaced with the name and sys_id of the target domain in the imported update set xml. When i am trying to import the application to one of the domain it successfully completes and able to use it. The same application is imported to the second domain with the necessary changes, it throws errors like 'Found local update set newer than this'. If i skip the error or accept the error and commit the update set, the application from first domain vanishes and appear in the second domain.

I want to explore the possibilities of application re usability in Service Now. Something like, an application developed in the development instance can be imported to different domains in the production infra. Please help me out in any way possible.

Mail : Arun.Rnair@techmahindra.com

Ph # +91 8884294547

[Chuck Tomasi]

Hi Arun,

To make an application domain aware, you should really be adding the domain and overrides fields to your app and using them the same way other apps are using them. Data is assigned to a domain, but apps are designed to work across all domains, keeping the data separate.

Domain Separation - ServiceNow Wiki

[Anson_Mayers]

Hi Arun,

From the description you've given, ServiceNow is pretty much doing what you're telling it to do. You've updated the domain name and domain sys_id, but you haven't altered the sys_ids of the records in your update set to be new, so when the set is applied, the existing records are being overwritten.

I don't think you can improve your design by re-generating sys_ids, because very little of the metadata in an app is domain separated. You're left with the nearly impossible task of building and maintaining some kind of sys_id regeneration table whitelist. Until that is perfect (realistically speaking, it will never be perfect) you'll be generating metadata that can load but can't run, trash that would clutter up your caches and drain performance at the least and prevent functionality from working at the worst. It doesn't sound to me like a viable approach.

Chuck's feedback is correct, basically. You're going about this in a way that is going to cost you dear in the long run -- as a simple for-example, every bug fix is going to have to be replicated to every domain where the app is installed. You're better off not inventing a different approach.

-aB

PS - Please mark Helpful, Like, or Correct Answer if applicable.