In the database schema, every table or view that OneData considers as a data object must have audit columns and triggers. When you create an object for the first time in OneData (using any option like Add Data Objector Update Schema), OneData automatically adds the audit columns and triggers to the object. The audit column information is used extensively in the various modules of OneData.

In the database, the audit columns or triggers might be dropped when you recreate an object in OneData after performing database actions like recreating the table for changing column order. Hence, after performing such database actions, you must ensure that the audit columns and triggers are present in the object.