Catalog Item is automatically captured into update set by the 'system'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2023 08:31 AM - edited 11-03-2023 08:32 AM
After Vancouver upgrade, we noticed that whenever you touch a catalog item now, say you modify a client script or a ui policy, there is an extra update included in your update set by 'system', which captures catalog item itself, even if you didn't touch catalog item. When compared to current, it shows no changes. Do we know why it started happening, and what the best practice is to go about it? So far we have been removing it from our update sets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2023 09:24 AM
Hi @Community Alums
There actually is a small difference between. The version of the catalog item is updated when you change for example the client script.
I wouldn't delete these from your update set.
Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 01:44 PM
What's the difference, though?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 07:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2024 10:50 PM
@Community Alumsany update/ solution on this issue?
