Manage structured records with tables, fields, relations and views

Open the target project from the project library, then choose Business data from the project tools in the editor. Create a table with a name and description. Nemeow automatically adds a Name primary field and an All records view so you can enter the first record immediately.

You can also describe what the first version should save in Build. The proposal shows a plain-language information summary. After one Confirm and build action, the server prepares and atomically applies the data plan before page generation begins. If data setup fails, page generation has not started and you can retry directly.

Tables, fields, records and views are constrained by both account and project: another account cannot access them, and another project in the same account does not display them.

Fields support text, number, boolean, date, date and time, email, phone, select and relation types. A date remains a calendar date; values such as CRM follow-up times are edited in the browser's local time and stored and returned as one canonical UTC instant with millisecond precision. Email accepts one ASCII address, not a display name or address list; its local part is preserved and its domain is stored in lowercase. Phone accepts 7 to 15 ASCII digits with an optional single leading plus and valid separators; it stores one canonical number string without inferring a country or carrier, verifying ownership or reachability, sending SMS, or placing calls. Configure allowed options for a select field. A relation can target only another table in the current project and cannot cross project boundaries.

Each value is validated against its field type. Save views with selected fields, filters and sorting for work such as leads to follow up, active projects or another operational slice.

The Business data workbench currently loads the first 500 records at a time; this is not a 500-record limit on App runtime access. Controlled Apps use approved backend operations with cursor pagination and server-side filtering and sorting. They can access only explicitly authorized tables, fields and record scopes, not all workspace data automatically.

Deleting a field also removes its values. Deleting a table removes its records and views, as well as relation values that point to it. Deleting the whole project also deletes that project’s business tables. An ordinary record cannot be deleted while another record references it, and the server does not list referrers: clear or redirect optional relations first; required relations must target another record, or the source record must be deleted. Export or preserve important information before a destructive change.

Schema changes must also respect the current App and retained Release compatibility rules. Review the latest structure after a conflict; a refusal does not mean deletion succeeded. Relations currently store one target record, not automatic many-to-many relationships. Formula, lookup/rollup, bulk writes and aggregation are not supported merely because a field or page mentions them.