Group type for "itil" has different sys_id

[kirkr]

We have upgraded our development environment from Geneva to Istanbul. While testing, we found that the project module didn't display all of our assignment groups.

After further research I found that the ScrumPPMIntManager script include is used to determine what groups appear, in particular ScrumPPMIntManager.getPhaseDotGroup(..) which looks for groups that have the type itil. It searches for the sys_id of 1cb8ab9bff500200158bffffffffff62

Within a fresh personal instance the group type of itil has the sys_id of 1cb8ab9bff500200158bffffffffff62

Our instances here have a different sys_id for the itil group type

To fix this for our instances, I've extended the ScrumPPMIntManager script include and overwrote the getPhaseDotGroup() method to include our sys_id, so it is working.

I checked both of the other group types for survey and catalog, those all have matching sys_id values.

My question is with the fact that our itil group type has a different sys_id, is there a way to resolve this properly or will I need to start making customization everywhere this is referenced in the system?

[Michael Ritchie · Accepted solution]

You could rename your ITIL group type to ITIL-old.   Then export the ITIL group type record from your personal instance: Pull up the record, click Additional Actions\Export and choose XML (This Record).   Then through retried updated sets, import that XML.   This is just a single record and NOT an update set so no preview and commit required.   This will get the record in your instance with the correct SysID.   Then update all the groups that have a group type of ITIL-old with ITIL and you should be good.   Then delete the ITIL-old group type.

I wonder if the original got deleted from your instance at one point in time and someone recreated it, thus having a different SysID.

Edit: Before deleting ITIL-old make a backup copy of this record using same method you used to get the record out of your personal instance.   This way you can bring it back in case of issues.   The problem with queries of groups on Group Type is that with a List type attribute it is searching based on the SysID so if you have any filters or code elsewhere that SysID may need to be updated.

[kirkr]

That's a good idea.

I'll put a ticket in to inquire, just in case it's a known thing. I keep digging and it shows it was created by the system on 2017-02-21 15:29:08 so it's very odd.

Looking at the upgrade history, that's around the time the Service Management Core plugin was activated.

I'll update this if I hear anything different.

[Michael Ritchie]

Yeah that is odd because the one in my instance has these dates:

<sys_created_by>admin</sys_created_by>

<sys_created_on>2015-06-02 23:02:03</sys_created_on>

For the interim to get you going you could just have both ITIL-old and ITIL associated to all groups.   That way code using either SysID will find them.

Please mark any post helpful and/or the correct answer to your question so others viewing can benefit.