Update Set Manager

Update sets live in every application scope, and hopping between the picker, the form view, and a second scope is a lot of motion for a small job. Update Set Manager keeps the list, the detail, and the actions in one dialog so you can stay on the page you were already editing.

Open It

Any of these opens the same dialog:

• /usm: the slash command
• The icon next to the update set picker in Classic and Next Experience
• The radial menu (Quick Ring)

What You See

The left sidebar filters the list:

• Scope: current scope, a recent scope, or All scopes
• Search: filter by update set name
• Status: In progress, Complete, or All

Every row shows the update set's application scope, so a filtered or scrolled list stays unambiguous. (In the All scopes view the group heading already names it, so the row leaves it out.)

The dialog always opens on the scope your session is actually in, not a scope you happened to pin last time, and selects the update set you are currently working in. That set stays in the list and marked as current even when the status filter would hide it, with an orange Default badge if it is a Default set. Filtering to another scope, or searching, is treated as a deliberate narrowing and is left exactly as you asked for it.

The dialog re-reads the session whenever you come back to it, so a scope or update set you changed in another tab is reflected without pressing anything. There is also a refresh button in the title bar.

Pick a set and the right pane shows its details: scope, parent, description, who created it, last updated, and whether it is the Default set. From there you can Make current or Open record.

If the set is a parent, the detail pane also lists the child update sets gathered under it, with the scope and status of each. Click one to jump straight to it, even when it sits outside your current filter.

Preview captured updates

Preview captured updates in the detail pane lists everything the set captured, newest first, 100 at a time with Previous and Next for the rest, so a Default set running to thousands of records is fully reachable. The filter box narrows by the changed record's name or its type, and the count next to it always reflects the filter you have applied.

Move captured updates to another set

Changes captured in the wrong update set, most often the Default set, used to mean editing sys_update_xml by hand in a list view. Instead, open Preview captured updates on the set holding them, select the records you want like a spreadsheet (Shift+click, Ctrl/Cmd+click, drag, or Ctrl/Cmd+A), and choose Move to update set, or drag them directly onto an update set in the list.

The destination list only offers in-progress, non-Default sets in the same application scope as the captured update, because a captured update belongs to the scope it was created in and would not preview or commit cleanly anywhere else. If the destination already captured the same record, you are warned before anything is written: two updates for one record means only the newest is applied when the set is committed.

Free vs Pro

Cross-scope actions

When a Pro action needs another application scope, the manager switches for you, does the work, and puts your original scope and update set back afterwards. Nothing reloads the page on its own.

Related

• /su: quick switch of an in-progress update set in the current scope (stays in the slash palette)
• Header pickers: Application and Update Set pickers in Classic and Next Experience