I want when we create update sets then reports should not captured in instances

[Anurag Tripathi]

Hi Aman,

Reports don't get captured in update sets, that is the oob behavior. Are you seeing different in your instance?

[Mark Manders]

Yes they do. OOB reports are captured in update sets.

[Aman Mishra]

i have xanadu version in this version i created one update set and set current.
when create report and save then that report is captures in update set

[Mark Manders]

ServiceNow uses the 'update_synch' attribute on dictionary level to decide if records should be captured in update sets or not and it is of very high risk to update it on any table (either adding or removing it).

The question really is 'why'? Why would you be creating reports on DEV in an update set and not moving them to another instance? If you need the report, you need to move it and if you don't need it, why create it?

If for some reason people just don't know what they are doing, just have some logic that if a report is added to an update set, it is moved to the default. That way you are not creating risky technical debt (with keeping everything in sync for patches and upgrades). But it really sounds like a people issue and it is never a good idea to resolve people issues with technology. Why aren't your developers checking their update sets before they are completed? That should be the number one rule.