Connection record not tracked in update set.

Afsar2 · ‎02-08-2022

Hi guys,

I noticed that Connection record are not tracked in update set.

I have also tried "Force to update set" but this particular record is not tracked.

I believe as there is a reference to Credentials, that could be a reason for this. But I could find any official doc on this topic.

Note: I was able to track "Connection and Credential Aliases".

Any suggestions on this?

shloke04 · ‎02-08-2022

Hi @Afsar

Connection records are data records only and Data records are not captured in an Update set. please refer to article below:

Refer the link here for more details which says clearly about what is captured and not:

https://docs.servicenow.com/bundle/rome-application-development/page/build/system-update-sets/reference/customizations-tracked-update-sets.html

There are two ways to handle this:

1) Either this need to be moved as a XML by exporting from Source instance and then importing it back in Target.

2) There is a SN Util feature name as "Add to Update Set" which I find it very handy for these scenario and can capture any data change as well along with updates . Please refer the link below for downloading it:

https://developer.servicenow.com/connect.do#!/share/contents/9824957_add_to_update_set_utility?t=PRODUCT_DETAILS

Let me know if you have a follow up query.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

View solution in original post

Community Alums · ‎02-08-2022

Hi Afsar,

Connection records cannot be captured in update sets even if you do "Force to update set".

There is no Official doc which i can give you right now, it came by experience in multiple projects.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

Afsar2 · ‎02-08-2022

Hi @Sandeep Dutta ,

I appreciate it.

Do you have any knowledge why so?

Afsar2 · ‎02-08-2022

I believe it is due to encryption as there is reference to Credential record.

But as there no documentation, it still the suspense for me.

Community Alums · ‎02-08-2022

Hi Afsar,

I will you a use case to understand: we had a third party document reader/signer integrated to servicenow. The connection and credential details can be found but won't help you anyway. As you will need to setup manually.

hence, Even if you want capture and move to next environment as part of update set,it won't capture, you will have to do it manually.

Mostly the credentials information is not captured as its a data. and Data never gets captured under update set.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep