- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2024 10:04 AM
Why is related list not captured in update set despite having update set in progress and selected from picker and making functionality changes under it ? I am trying to move update set from dev to test instance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 08:50 PM
Few points to check
Update Set Scope: Ensure that the related list changes are within the scope of the update set. If the related list changes were made outside the scope, they won't be included. Double-check the scope settings of the update set to ensure all necessary changes are included.
Dependencies: Related lists often have dependencies on other elements such as UI policies, UI actions, business rules, or scripts. Ensure that all dependencies are also included in the update set. If any dependencies are missing, the related list might not function correctly after migration.
Manual Addition: Sometimes, related lists and their dependencies need to be manually added to the update set. Even though you've made changes under the update set, certain elements might not be automatically captured. Review the related list configuration and its dependencies and add them manually to the update set if necessary.
Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 07:55 AM
On incident table, I have created a relationship script to show CIs affected by that particular incident. so when you open an incident, all CIs affected by that incident will show on the related list.
While i migrate my update set from dev to test instance - - commited update set , I dont find related list on the test instance after update set installation (state is commited for update set)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 10:09 AM
Is there any difference in scope? Alternatively, you can replicate the same on test and prod.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 10:03 AM
Hi @Snehal13 ,
Try adding the related list in form and check if the entry is captured in the update set. It will capture in the update set. Also if it is not moved in the update set you directly configured on a form level by configuring related list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 08:50 PM
Few points to check
Update Set Scope: Ensure that the related list changes are within the scope of the update set. If the related list changes were made outside the scope, they won't be included. Double-check the scope settings of the update set to ensure all necessary changes are included.
Dependencies: Related lists often have dependencies on other elements such as UI policies, UI actions, business rules, or scripts. Ensure that all dependencies are also included in the update set. If any dependencies are missing, the related list might not function correctly after migration.
Manual Addition: Sometimes, related lists and their dependencies need to be manually added to the update set. Even though you've made changes under the update set, certain elements might not be automatically captured. Review the related list configuration and its dependencies and add them manually to the update set if necessary.
Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.
Thanks