- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2023 07:29 AM
In other words, what determines that certain records (Incidents, Users, certain scripts etc) are captured in Update sets but others are not (presumably Groups, Roles, user settings or preferences?)
If I build a custom application in Studio, is there any way I can define a table as containing base data or transactional data? Last time I built an application and used Git for source control, all the tables had been wiped when I moved the app to my PDI. It would be nice if I could avoid that in the future, but I also just want to understand how it works.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 01:13 AM
I would refrain from using update_synch nowadays, this is a bit outdated. Since we introduced scopes and 'Applications'.
What is Metadata in ServiceNow?
The sys_metadata table and its extensions are the tables that contain records defining system configuration that determine how the platform behaves. These records are sometimes referred to as Application files. By extending sys_metadata, the configurations inherit scope awareness and are automatically included in applications and update sets.
How does Metadata relate to update sets?
Prior to applications, the only mechanism of deploying configurations to other instances was via update set. The update set contained a collection of sys_update_xml records with payloads that defined the record to be updated. Historically, the update_synch attribute controlled the inclusion of a particular table in an update set.
When applications were introduced and sys_metadata created, the use of update_synch independently is no longer permitted. It should only be used on sys_metadata extensions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2023 07:48 AM - edited 07-31-2023 07:55 AM
Hello @kim-lindgren
It depends on update synch dictionary attribute on the table.
refer below doc:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0535262)
Please hit the thumb and Mark as correct based on Impact!!
Kind Regards,
Ravi Chandra.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 01:13 AM
I would refrain from using update_synch nowadays, this is a bit outdated. Since we introduced scopes and 'Applications'.
What is Metadata in ServiceNow?
The sys_metadata table and its extensions are the tables that contain records defining system configuration that determine how the platform behaves. These records are sometimes referred to as Application files. By extending sys_metadata, the configurations inherit scope awareness and are automatically included in applications and update sets.
How does Metadata relate to update sets?
Prior to applications, the only mechanism of deploying configurations to other instances was via update set. The update set contained a collection of sys_update_xml records with payloads that defined the record to be updated. Historically, the update_synch attribute controlled the inclusion of a particular table in an update set.
When applications were introduced and sys_metadata created, the use of update_synch independently is no longer permitted. It should only be used on sys_metadata extensions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 01:43 AM - edited 08-01-2023 01:43 AM
Thanks for the clarification. Linking to my response in this thread for the full context of this discussion.
