Entity
A table of data in a Base44 app that holds one kind of thing, like tasks or bookings.
Also called data table.
Every app is secretly a pile of lists. A gym app has a list of members and a list of bookings. In Base44 each list is an entity, and each booking is one record in it.
You describe the fields once, in a schema. Usually you say it in plain English and the builder writes the JSON. Every record also gets id, created_date, updated_date and created_by for free, so don't add your own copies.
Two mistakes I see a lot:
- One giant entity called Data with a field for everything. Split it, one entity per kind of thing.
- Trusting
unique. Base44 stores that setting and ignores it. If duplicates matter, check for them yourself.
And the one that hurts: a new entity with no access rules is open to everyone. That's what row-level security is for.
Related:Row-level security and BaaS.
Where I've used it: