Settings storage and sync

DataMind Oda keeps its settings on this computer, on top of the values it ships with. This page explains where they live, how a page reads and refreshes them, what happens when the settings change while you edit them, and what a read-only deployment changes. To open Settings and find your way around the panel, see Settings overview.

Where your settings live

Oda records the settings you change on this computer; everything else comes from the values Oda ships with.

• The file behind them. The profile settings file covers the file your settings are kept in, and with Developer tools on, Developer settings can open it for you.
• Your value versus the default. A field holding your value carries the Overridden badge.
• Company-held values. A row your company manages reads Managed by your organization, with the reason beside it, and it cannot be changed on this computer. Permissions, approvals and feature controls covers company locks, and Advanced features shows them on the feature switches.

Take a value back to the default

1. Find the field holding your value: it carries the Overridden badge.
2. Choose Reset to default beside it. The reset is staged, like any other change.
3. Choose Save. The reset is written like any other change, and the field follows the value Oda ships with again.

A reset clears only your value; whatever Oda supplies beneath it applies again.

The same steps work on plugin cards and forms, such as those on Live plugin settings.

What writes a change

• Only a save writes. A change on a settings page or form is staged while you edit; nothing is written until you save it.
• Leaving a page drops your unsaved edits. A plugin's settings form has no separate discard control: what you edit but do not save simply does not apply, so save before you leave a page you changed.

When a page reads your settings

• When you open it. A settings page reads the current values as it opens.
• While it stays open. A page that stays open refreshes in place when the settings change elsewhere.
• When a window regains focus. Oda reads again when the connection to its server returns and when a window regains focus, so a change saved in one window reaches another window the next time it regains focus or reconnects.

If the settings changed before you saved

Every save carries the settings as your page read them. If the settings changed after that, the save is refused and nothing is written; your edits stay on screen, and the card reports the conflict. On the Models page the card reads Someone else changed these settings while this card was open. Close it and reopen to edit the current values.; other cards word it their own way.

1. Close the card.
2. Open it again. It reads the current values.
3. Make your change again.

Models in the chat picker shows this on the Models page, and Live plugin settings covers the same for plugin forms.

Read-only deployments

A deployment can store its settings read-only. The pages still open and everything can be read, but the controls that would change a value are disabled: switches, fields and buttons such as Save, Refresh and Apply.

• The page says why. The built-in cards read This deployment stores settings read-only.; the Models page reads The settings document is read-only in this deployment.
• If a value must change, ask your administrator. Nothing on the page changes the read-only state.

Questions, answered

Where do my settings live?

On this computer. Oda records what you change on top of the values it ships with and reads them back from there. The profile settings file covers the file itself, and Developer settings can open it for you.

Why doesn't another window show my change yet?

A change saved in one window reaches another window when that window regains focus or reconnects. Oda also reads the current values when a window opens a page, and an open page refreshes when the settings change. If a page still shows an older value, open it again.

Why did a settings card ask me to close and reopen it?

The settings changed after your card read them, so the save was refused as a conflict: nothing was written and your edits stay on screen. Close the card, open it again to read the current values, and make the change again.

Why can't I save anything on a settings page?

The deployment stores its settings read-only. The pages open and everything can be read, but the controls that would change a value are disabled; the page says why, with This deployment stores settings read-only. or The settings document is read-only in this deployment. If a value must change, ask your administrator.

Why does a setting say Managed by your organization?

Your company holds that value. The label shows with the reason beside it, and the control cannot be changed on this computer. Ask your administrator if you need it changed; Permissions, approvals and feature controls covers company locks.

What do pages show while Oda is disconnected?

They keep showing the values they last read. When the connection returns, Oda reads again and updates the page. The connection pill beside Settings shows the state; Settings overview describes it.