Transferring groups from one instance to other

[naga7777]

Hi All,

I created new update set and created a group. But when i go to the update set, group is not showing in the update log to commit. Can anyone please help me about transferring groups from one instance to other instance?

Regards,

NagaDinesh.

[Chuck Tomasi]

As the others have stated, you cannot capture groups in update sets. They are considered 'transactional data' that is modified in production, like incidents, or user profiles. You will need to export/import the XML. Not only for the group, but likely for the group memberships as well. To ensure all the sys_ids align, you may also want to get the users as they may have different sys_ids between systems, depending how you imported your data in dev/test.

The tables involved are:

• Groups: sys_user_group
• Users: sys_user
• Group membership: sys_user_grmember

This document provides a step by step how to do the XML export/import. http://wiki.servicenow.com/index.php?title=Exporting_and_Importing_XML_Files

[alexmitchell]

Hi Chuck

Your mention of sys_id is a KEY point here. We have found that exporting from sys_user_grmembers via XML from Test and importing into Prod actually adds the “first” user, by created date, with a matching name to the group if the sys_ids are not consistent across environments.

hence we have the wrong “Joe Bloggs” as a member of a group!

is this a known issue? Defect? Feature?

[madhu_serviceno]

Hi Chuck,

I need your suggestion on migrating the groups between the ServiceNow instances. My organization has decided that for every new local group created in the child developer instance, they want to create a group in AD directory and want to create groups through LDAP integration in dev(parent),test,prod ServiceNow instances. As far as for the development code practices, they would like to use the group name instead of sys_id's(as different sys_id’s are generated in the instances when the group is created). Is this a good practice? They decided not to use the export/import the XML process for migrating the groups between the instances. Please suggest the best practices and your recommendations on how this can be addressed. Any input is greatly appreciated!

[naga7777]

Hi All,

Thanks a lot for your help. Solved my problem

Regards,

NagaDinesh.

[HugoFirst]

Hello Naga,

As usual, Chuck has given you great advice and I remind you to mark his reply as Correct.

That said, I have recently uncovered a utilitiy that will allow you to capture a group, user or any other kind of record in an update set.

I've used it for 2 dev/test/prod cycles and it works great.

It is called the "Add to Update Set Utility" and it is available on the Share site.

Link:   ServiceNow Share

I'm trying to give you a link to the utility itself, but it may take you to the general share site.   If that happens, just search for "Add to Update Set Utility".

It places an "Add to Update Set" button on every record.   If you click the button, the record is added to the update set.

FWIW:   I changed it from a button to the right click menu item.   There was too much chance of adding something I didn't need, to the update set with a button.