Configuring OData Model

Configuring OData Model

ODataDB allows configuring application features with the SaveToDB Framework.

In short, SaveToDB Framework is a set of special tables used to configure features.

You can easily install it on any supported database platform.

Two of our products, DBEdit and SaveToDB add-in for Microsoft Excel, also use this framework.

So, you can configure features once and use Microsoft Excel, a desktop DBEdit app, or an ODataDB JavaScript client to view and edit data.

ODataDB supports a subset of application features available in SaveToDB and DBEdit.

For now, it supports only the following configuration tables: xls.objects, xls.handlers, and xls.translations.


Use the xls.objects table to specify target tables or stored procedures used to save changes using the Save button.

See an xls.objects sample and the generated model.

You can add stored procedures into this table to change its type from ActionImport to FunctionImport if ODataDB detects the type incorrectly.

Also, you can add SQL-code objects here. For example, you can see the s02.code_cashbook object. You can try it.

See also:


Use the xls.handlers table to configure:

  • Value lists for column dropdowns (ValidationList and SelectionList)
  • Value lists for parameters (ParameterValues)
  • Cell change handlers (Change)
  • Columns with checkboxes (BitColumn)
  • Disabling the Save button (DoNotSave)
  • Disabling the Insert Row and Delete Row buttons (ProtectRows)

See an xls.handlers sample and the generated model.

You can see more handler types than supported, as this is a sample for the SaveToDB add-in.

See also:


Use the xls.translations table to translate names of objects, columns, and parameters.

See an xls.translations sample and check the ODataDB.DisplayName annotations in the generated models in English, French, Spanish, Italian.

You can try the same procedure in different languages and locales (change and save data on one page, and reload data in another one):

See also: