Using direct writeback and named sandboxes

By default, IBM® TM1® is set to use a direct writeback with named sandboxes. Your Administrator may have set your work options to something different.
A 3-column table that shows the personal workspace and sandbox settings.
You want to Personal workspace mode Sandbox
Have data changes update the server immediately. Occasionally, you want to save a set of changes and name them before committing them to the server. Off On

When you have direct writeback and named sandboxes the toolbar starts out with the Commit and reset Data buttons grayed, the Sandbox button available, and the sandbox list area displays [Base]:

Toolbar that shows the icons available when using writeback.

The Sandbox button indicates that you can create and delete sandboxes. The Commit button is grayed but is present because there is nothing to commit yet. If you made a data change and decided to save it in a named sandbox, Commit and Reset Data would become available. Cell coloring would only change when you named a sandbox. Until you name a sandbox, you are operating in the base.

If Job Queuing is turned on, submitting the sandbox to the server is subject to queue processing before the data changes are committed.