Catalog Item captured in update set automatically when updating related records of the item

[arundharmabe]

Hello Everyone,

The Catalog Item is getting captured into the update set automatically when updating related records of the item such as Catalog UI policies, Variables, etc. 

For Ex:

When developer 1 is working in dev instance and still development is pending on the item. Meanwhile for some other work, if developer 2 just updates only the catalog UI policy of the same item, which automatically captures developer 1 updates as well in to the developer 2 update set. Due to this, the pending work/development from the first developer is also captured by second developer and moved to Production. This is impacting the existing logic of the item.

Has anyone have a solution to avoid this behavior? Kindly share.

Kind Regards,

Arun

[Hemanth M1]

Hi @arundharmabe ,

You can try below options

1)Why don't you remove catalog item customer update entry and move only other component

ex:

2)Before capturing client script or any component revert to production version, update component (developer 2) and move update sets to prod, come back to dev and rever devloper 1 version.

Hope this helps!!!

[arundharmabe]

Hi Hemanth,

Thanks for the response.

Already i was doing the manual work but would like to see if there are any options to avoid the same. In case if i want to do bulk number of updates then it would be hard for me to check what should be there in update set and what not.

Kind Regards,

Arun