How to preserve the custom inbound integration during cloning?

[Venkatesh4]

Hi All,

We have two custom inbound integrations and I am unable to find a table where they get stored.

So during cloning will they get erased?

If So how to preserve them?

[Community Alums · Accepted solution]

Hi Ventatesh,

Go to System Definition > tables

All the tables which starts with prefix u_ are custom tables.

so look for your custom table here.

To preserve the details:-

I believe you can identify tables that you want to save/exclude in your clone configuration; However I would be inclined to simply export XML for the tables I wanted to keep (or updatesets if you have used them) and then reload post clone. Another approach with updatesets is to close them out, import to prod but don't deploy, then deploy on your sub-prod instance post clone.

Learn more on data preservation from here:

https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/managing-data/concept/data-preservation.html

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Venkatesh4]

Hi Sandeep

Thanks for your response

I would like to understand that this inbound integration WSDL link is pointing to our UAT instance.

But I am worried that after cloning this will be overridden by Prod WSDL link.

Also the WSDL filed is not editable.

Can we preserve the inbound integration?

[Appli]

Hi, what exactly the type of Inbound Web Services do you use? RestAPI, Scripted RestApi, SOAP WS, ..?

Is it custom or OOB?

Hope it helps