CMS
Indholdstabeller, som dine hjemmesider og apps læser.
En CMS-tabel er en almindelig tabel i arbejdsområdets database. Du administrerer tabeller med CMS-metoderne, og du læser og skriver deres records med record-metoderne. Hvert kald er et POST til /cpi/<method> med en JSON-body, der bærer din API-nøgle.
Svaret rummer hver tabel med dens felter og antal records og den database, den ligger i (det app_id, record-metoderne tager).
Fra dashboardet
Hver tabel har et API-vindue: tryk på API og JSON på et kort eller i en åben tabel. Det viser de fem record-kald for den tabel, tabellens egne felter som JSON, den samme forespørgsel som cURL eller JavaScript og et sted at sende den. Dets nøglevælger viser de nøgler, der når arbejdsområdet, og kan lave en ny. En nøgle med fuld adgang virker. En tilpasset kræver dbs_read for at læse og dbs_create, dbs_update og dbs_delete for at skrive.
Records
Vinduets fem kald kører disse metoder. Hver tager arbejdsområdedatabasens app_id og tabellens id.
En record er et objekt, hvis nøgler er tabellens felt-id'er. Send table_data som et array for at tilføje flere records på én gang. Sletning flytter records til Arkiverede, og dbs_restore med de samme id'er bringer dem tilbage. Tilføj permanent for at slette dem for altid.
DBS Read
Reads records from an app table with optional row range, single-row lookup, sorting, filtering, and archived-record selection.
DBS Create
Creates a new record in the specified app table from the provided key-value table data.
DBS Update
Replaces the data of an existing record, identified by row_id, in the specified app table.
DBS Delete
Soft-deletes (or permanently deletes when 'permanent' is set) the listed record IDs from an app table.
DBS Restore
Restores previously soft-deleted records, identified by their IDs, in the specified app table.
Tabeller
Get CMS Tables
The CMS tables of one workspace, active and archived, each with its fields and how many records it holds, plus the database the records live in (the app_id to hand dbs_read, dbs_create, dbs_update, dbs_delete and dbs_restore), whether that database is ready, and the plan with what it allows. The first open of a workspace other than Main installs the database plugin there and answers preparing until it is ready.
Get CMS Table
One CMS table as Xuda Studio stores it (its fields and indexes), with its record count and the database it lives in.
Save CMS Table
Create a CMS table, or change one when table_id is sent. A table has a name, an optional description and its fields, each a name, a type (string, number, boolean, date, array, object, or relation) and whether it is required. A relation field relates the table to the Contacts module ({ kind: 'module', module: 'contacts' }) or to another CMS table of the workspace ({ kind: 'table', table_id }), holding one id or, with many, several; a saved relation keeps what it relates to and its shape. Field names start with a letter and use letters, digits and underscores. A new table counts against the plan's tables, and every table against its fields per table. The table is an ordinary Xuda Studio table in the workspace's database, so it opens in Studio too.
Archive CMS Table
Archive a CMS table (it leaves the list and its records stay) or bring it back with archived false, which counts against the plan's tables again.
Get CMS Records Of An Item
The CMS tables related to one item of another module (a ticket, a delivery, an order, a product, a finance document or a contact), each with its fields and the records that point at that item, so the item can show them to fill. A workspace with CMS switched off answers no tables.
En ny tabel tæller med mod din plans tabeller, hver tabel mod sine felter, og tilføjelse eller gendannelse af records mod dens records. Et kald ud over en grænse afvises med en meddelelse, der siger hvilken.