Question about Incident Table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2024 03:01 AM
Working for a company that would update their instances, but would skip records.
When I started, the instances had hundreds of updates available they had never installed.
They finally updated the instances, with some, but not all updates.
They are having random problems with the Incident module.
The Incident table shows in the Versions tab of the table, with an update set / version back in 2019.
Comparing it to my PDI, aside from fields they've added, there are field missing/extra that don't match up to the PDI.
Does this mean this IS the current version of that table? Is the version tab only showing Update set version?
How do you find out what actual version this table is on?
If I look at the PDI, go to the Incident table, then select Copy SysID, if I compare it to two different PDIs I have access to, they are the same. But they are not the same between the PDI and this company's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2024 09:13 PM
Hi @LKSN
1. Versions Tab
- The Versions tab under the Incident table shows records of when the table itself or any of its attributes were updated. This can include updates from update sets, manual changes, or system upgrades. The date you see here (2019 in your case) indicates the last recorded change to the table schema or fields but doesn’t necessarily correlate directly with the platform or module version.
2. Update Sets
- Update sets are bundles of configuration changes that can be moved between instances. They do not typically include all foundational updates but rather the changes you’ve made or decided to import. If fields in the Incident table have been removed from or added to update sets, this could lead to discrepancies.
