Should sys_id match across instances for groups?

juan casas · ‎08-03-2022

Should the sys id of groups match across all instances (dev,prod,test)?

For some reason, we got a group that does not have matching sys ids across the instances,

I send the issue to ServiceNow and they said that this was OK?...... which seem really odd

Then we have big time Chuck, AKA ServiceNow OG AKA ServiceNow GOAT with the following post::

Chucks post answer:: https://community.servicenow.com/community?id=community_question&sys_id=7b4f4fe1dbdcdbc01dcaf3231f961981

servicenow post:: Compare local update sets (servicenow.com)

Mohith Devatte · ‎08-03-2022

Hello @juan casas ,

so to explain this case its better if you have group sys_ids same across the instances .

Reason: lets say you have createD a group in DEV and you used the sys_id it in some script to compare group sys_id value

But you have created a same group with same name in TEST or PROD environment with all same configurations but in this case it creates a unique 32 bit sys_id in that particular instance which will not be same as dev

and when you move your code to test or prod your code might not work because you must have compared with dev group sys_id .

Best practice is export it to xml and then move it other instances instead of creating them in other instances as these are transactional data and not captured

IT ALWAYS MATCHES THE NAME AS THE UNIQUE ONE BUT NOT THE SYS_ID

PLEASE MARK MY ANSWER CORRECT IF IT HELPS YOU

View solution in original post

juan casas · ‎08-04-2022

everyone was wrong cuz if you have active directory its ok