Rename an update set that is already completed and moved to production

[JC S_]

Since there was no naming convention policy set when our developers started using update sets, we are planning to tidy up the update sets by renaming them however we can only rename them on development instance but not the ones on our production. Can we force rename the update sets via a fix or background script or is there any other recommended approach to this problem?

[Aman3]

Hi JC,

Yes you can rename those, they have already been migrated to production. Any new changes will be captured in new update sets.

Have done many times in the past without any issues.

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

Thanks,

Aman

[JC S_]

Hi Aman,

So you've used a background script to rename the ones on production? If yes, can you share it? Currently all fields in the retrieved update set is set to read-only.

[Aman3]

Hi JC,

Here is the snippet.

var gr = ne GlideRecord('sys_remote_update_set');

gr.get('07cb42c7db7b3a0072a6721dbf961981');

gr.query();

if (gr.next())

{

gr.name='New name';

}

gr.update();

Thanks,

Aman

Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.

[JC S_]

Hi Aman,

Just tried this and it didn't work.