Default Fields
Default fields are used to define the fields that all tables or most tables in the model need to contain. When set to default and auto-apply is enabled, new tables will automatically carry these fields to ensure that common fields are not missed. The difference from entity/table template is that the template defines the shape of the entire table hierarchically, and the default field defines only the field itself.
Define default fields
- Opens the Default Fields editor.
- Add default fields to maintain field names, Chinese names, data types, and other properties.
- Check Automatically apply to new tables.
- settings saved.
The diagram shows the default field editor. The focus of the diagram is that "Automatically apply to new tables" is the switch to make the default field effective. When not checked, the default field is only registered.
Instances
| Setup | Valid for | Ineffective for |
|---|---|---|
| Default field + automatically applied to new table | New table created after | Created table |
The default fields are saved according to the model, and are uniformly effective for new tables created in the same model.
Fit with templates, bulk editing
- When you need to supplement the default fields for an existing table, use Entity/Table Template to refresh, and the template refresh will also fill in the default fields defined in the template.
- When you first need to find out which tables are missing public fields, use Bulk Edit to list the tables by object type and check the fields.
- The default field name should be consistent with the Naming Settings specification to avoid non-compliant field names in new tables.
Notice
- When Auto Apply to New Table is unchecked, the default field is not automatically populated with new tables.
- When the default field has the same name as an existing field in the table, the new table is not added repeatedly.
- The default field does not participate in additional changes to the DDL, only affects the field composition of the subsequent new table.