Schema Editor

Applies to: supported App Generation projects and accounts that show DB Schema

The DB Schema page displays the generated application data model. It is not a standard control for every App Generation account.

If your project navigation does not show DB Schema, use Edit via Chat to request schema changes.

What the schema editor changes

The schema editor can change these application definitions:

  • entities.
  • fields and field options.
  • relationships.
  • entity display types.
  • selected project schema settings.

These definitions control generated application behavior. They do not provide general database administration for the hosted VM.

Open the schema editor

  1. Open a supported App Generation project.
  2. Find DB Schema under Editor.
  3. Open the page.
  4. Confirm the displayed environment before you make a change.

If the link is absent, the editor is not available for your current project and account.

Add or change an entity

Use a clear singular name. Add the required fields, display labels, and relationships.

Choose a view type that matches the record workflow. Calendar and kanban views need suitable supporting fields.

Read Create a Generated Application Schema and Data Representation: View Types.

Change a field

Confirm the field type, required state, uniqueness, label, and list visibility. Check all forms and views that use the field.

Changing a field type can require data conversion. Removing a field can remove access to stored values.

Save and verify

  1. Review the complete schema.
  2. Save the schema change.
  3. Wait for the application change process to finish.
  4. Open Edit via Chat.
  5. Test forms, views, filters, relationships, and permissions.
  6. Save a project version after successful testing.

The exact save and application process can depend on the project version. Follow the status shown in the project.

Use AI Engineer when the editor is unavailable

State the entity, field, relationship, and required data behavior in one request.

Example:

Add a required renewal date to Contract. Show it in the table and preserve all existing contract records.

Review the applied migration and application behavior. Do not assume that a successful code change also preserved every stored value.

Protect application data

Save a code version before a major schema change. Export important application data before a destructive operation.

The schema editor is not a database backup. A code version does not contain the complete database.

Do not use Drop DB and Rebuild for a normal schema change. That action can delete generated application data.