Catalog builder update set name cut off

[Vincent Schmie1]

Hey all,

I ran into the issue, that the catalog builder creates update sets automatically and chooses the name in a very simple manner:

CB_<Name of the template>_<Name of the item>_<Date & time>

The issue with this: Update set names are cut after a certain amount of characters. This makes destinction between them very hard when you import 2 or more with the exact same name to the next instance.

I would like to change the names of the update sets to this

CB_<Date & time>_<Name of the item>_<Name of the template>

From most specific to least.

But I do not find any place I can configure this. All of the script includes are protected where I suspect the name generator is placed. Does anybody know where you could configure this?

[Paul Curwen · Accepted solution]

There is a max length OOTB of 80 characters on an Update Ste name. Good enough for most purposes, but I can see your issue here. . Easy extended if needed just go to the sys_update_set table and increase the length on the string column to a sensible number. 

Either that, or start using short template names. 

[Vincent Schmie1]

Hey Paul, thanks for the advice. I am already down to a length where differentiating or identifying the purpose of those templates gets hard... but there is always this one next user who has an even longer name for their catalog item 😉

Changing the field length of the sys_update_set table will get me into discussions with my platform team that will make nobody happy 😄

So I still need a more direct configuration 😕

[Vincent Schmie1]

Hey Paul, thanks again for the advice. We will be moving along with increasing the length of the field and fingers crossed: nobody finds a way to create catalog item names longer than allowed 😉

[Brad Bowman]

Hi Vincent, 

We've recently come across the same issue.  Since template names can be up to 4000(?) characters, and catalog item names 100, we decided not to risk a skipped record on our next upgrade by altering the name field on the sys_update_set table.  What you can do instead, before promoting the update sets to the next environment is:

1) manually rename the update sets as part of the pre-deployment procedure, or

2) Batch the update sets by creating a new update set and setting the parent of every related Catalog Builder update set to the new update set - then you just deploy the one new update set that has the name you gave it, and you don't have to decipher / worry about the order. 

Update Set Batching