- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2023 11:50 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2023 03:01 PM
Hi, can you clarify your use case\business requirement, as I would suspect reporting on system audit\history data in this manner could result in performance issues.
Also, I would not recommend sys_history_set as a suitable reference for reporting, as this is not the intention of the data\table.
History sets - How are they generated - Support and Troubleshooting (servicenow.com)
What exactly are you trying to do and why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2023 03:01 PM
Hi, can you clarify your use case\business requirement, as I would suspect reporting on system audit\history data in this manner could result in performance issues.
Also, I would not recommend sys_history_set as a suitable reference for reporting, as this is not the intention of the data\table.
History sets - How are they generated - Support and Troubleshooting (servicenow.com)
What exactly are you trying to do and why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 06:28 AM
I have a request from a stakeholder to see the history of assignee changes on the catalog task tickets in the one-time report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2023 12:52 PM
Hi, I would look at tracking assignee changes as a metric.
Then if you really need to deliver details of historical assignment, run a 1 off script to populate metric instances from historical sys audit data.