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

Afsar2 · ‎02-09-2022

Please follow this screenshot.

shloke04 · ‎02-09-2022

Nope this should not happen. Have tested it again it does not create any batch or parent. See screenshot below:

Try creating a new local update set and then try again, may be there was some other issue in the instance but this Update set utility will not do so automatically

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

Afsar2 · ‎02-09-2022

I think it's happening for me because of custom scope.

Can you please check that?

shloke04 · ‎02-09-2022

Agree yes it does for Scoped Application, if you create an update set in a scope. But I don't think that should be an issue , it should make it easy for deployment only.

I have checked the notes of this utility as well and it confirms for scoped application it will create Batching for easy deployment:

See screenshot below:

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

Afsar2 · ‎02-12-2022

Great thanks @shloke04 .

The information is valuable.

I appreciate it.