Error: Can not add new update_sync attribute to a dictionary entry

[nikita_mironov]

I'm trying to make an existing table transportable via update sets setting "update_sync=true" in collection dictionary record. To be more specific I need to make schedules and schedule entries transportable via update sets as I'm starting using them in SLAs which already are trasported from DEV to QAS and PROD via update sets.

When I set "update_sync=true" I get an invalid update with an error "Can not add new update_sync attribute to a dictionary entry" triggered by Dictionary table Business Rule "Update Sync Check" that appered in Winter Stable 3 2010 release. It is as follows:

Condition: current.attributes.changes();
Script:
var hadAttribute = (previous.attributes && previous.attributes.indexOf('update_sync') < 0);

if (current.attributes.indexOf('update_sync') >=0 && !hadAttribute) {
current.setAbortAction(true);
current.attributes.setError("Can not add new update_sync attribute to a dictionary entry.");
}

Question to Service-Now: Does it mean that I no longer can make table transportable via update sets? Why?

[Mark Stanger]

The short answer to your question is 'Yes', but this is a question that really ought to go to support. This attribute actually causes quite a bit of trouble on high-volume tables so there has been an attempt made to lock it down. If you feel that you have a good reason for adding it to a particular table then its best to contact support and let them know why. They can help you to get the attribute added and, maybe more importantly, they could add it to the core product if its something that more people will need.

[nikita_mironov]

Thank you Mark. I'll raise question in /hi.

[agarwm]

Hi,

The attribute name for making a table tranportable via update sets is "update_synch" and not 'update_sync'. My guess is that might be causing the error.

Thanks,
Mayank

[john_andersen]

FYI: http://wiki.service-now.com/index.php?title=Update_Synch#Tracked_Customizations

And please note: The Winter 2010 Stable 3 release introduced a rule that blocks the use of the update_synch attribute in any table in which it is not predefined.

See the reasoning behind this change at the link I provided above.