Run an Update Set Once Clone Completes

jmiskey · ‎02-14-2023

We have a situation where we have scheduled a weekly clone from our PROD environment to a special DEV2 environment that was set up for us. We have created some Custom Themes that we would like transferred to this DEV2 environment. We tried setting "Preservers", in hopes that the Clone would not overwrite these Custom Themes, but it did not work (and research into old Community questions seems to suggest that this may not work quite as expected).

So we have a different approach that we would like to try. We want to create an Update Set that we import, but do not Post/Commit, in our PROD environment. Then, the Clone should copy that uncommitted Update Set to the DEV2 environment. We would like to then run this Update Set once our Clone is completed. So we have a few questions regarding the best way of doing this, including:

- What is the best way of running this Update Set once the clone is complete?

- Would you do that with a Scheduled Job, or in some other manner?

- Can a Scheduled Job actually run/commit an update set?

- If it can be done with a Scheduled Job, is it possible to make it wait until the Clone is complete, or do I just need to pick a time to run it when I know that the Clone should be complete (in a perfect scenario, it will run automatically upon completion of the clone)?

Thanks

Kirby R · ‎02-16-2023

Customer Update name is basically <table_name>_<sys_id of the record in that table>. So what you need to do is add these tables in your preservers similar to what you have done for sys_properties.

Example:

sys_ux_style, m2m_theme_style

You can do more granular and include the sys_id in the filter in your preserver

View solution in original post

jmiskey · ‎02-15-2023

From my post from yesterday, we are backing away from the "Update Set" idea, as it does not seem like a good solution. So we are just trying to figure out why this "Preserve" method is not working, as if we get that working, then there is no need for the "update set" method we described.

As you said, it looks like we set it up the preserver correctly and clone correctly (I used those two articles you referenced when I set them up). However, it does not appear to be working. When the clone is completed, the Custom Theme we had in the target environment disappears. Does anyone have any idea why this is not working? Did we miss something?

Seems like it might be a bug that we need to submit a HI ticket for.

Bert_c1 · ‎02-15-2023

I agree, if the 'Preserve your custom Next Experience theme during clones' configuration from the documentation is not working along with the "Preserve Theme" option, then create a Support Case.