values of sys_package and sys_user_role

[Siva28]

<sys_package display_value="Project Management" source="com.snc.project_management_v3">7f8290c9ecc85d04b430e0a382687bd2</sys_package>

<sys_user_role display_value="it_project_manager" name="it_project_manager">e2ac29723732310033cb26877e41f18e</sys_user_role>

I understand that the bold values or sys_id of the mentioned Application (Project Management) and the role (it_project_manager) but I am wondering why does this value change when I take an upgrade.

I am trying to resolve the skipped file. I see a different sys_id now in the upgrade version. What action should I take.

Upgrade version sys_id

<sys_package display_value="Project Management" source="com.snc.project_management_v3">276be5323732310033cb26877e41f17f</sys_package>

[Mark Stanger]

The 'sys_package' table is only relevant to your plugin files.  There should never be any reason to modify those records except through a plugin activation.  I would just take whatever the default action is there.

[Siva28]

Thanks Mark. But we have modified several records related to plugins and are trying to resolve these skipped files.

The current record sys_id (7f8290c9ecc85d04b430e0a382687bd2)is found in our sys_package table. But the sys_id coming from the upgrade(276be5323732310033cb26877e41f17f) is not found in the sys_package table. How is this sys_id resolved.

who uses this sys_package. What are the implications if I resolve by taking the upgrade file.. or if I resolve by not taking the upgrade file.

[Mark Stanger]

ServiceNow is the only entity that does anything with the 'sys_package' table.  All it is is a listing of the plugins you have activated along with a listing of the updates that are part of that package.  The sys_id for my 'sys_package' record in my system is different from both of the ones that you've got (which means that the sys_id itself isn't significant to its function (other than to provide a link to the individual components in your system).  If you're really concerned about whether you should commit it or not, you should see if there's anything else in the upgrade that references the same sys_id somewhere.