> For the complete documentation index, see [llms.txt](https://docs.objectra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.objectra.com/documentation/what-is-a-field.md). # What is a Field? ## Field Settings Explained This page explains the settings you’ll see when adding or editing fields in your database. Most people only need the **basic settings**.\ Advanced options are available if you need more control, but they’re completely optional. *** ### What is a Field? A **field** is a single piece of information you store about something. Examples: * Name * Email address * Date received * Status * Price Fields are reused so your data stays consistent and easy to manage. *** ## Field Settings Reference This table explains every field setting you may see when building your database. You do **not** need to understand or use all of these. Most users only need the **Beginner** options. Advanced settings are clearly marked and optional. *** ### How to read this table * **Beginner** – Safe and commonly used * **Advanced** – Optional, more control * ⚠ **Dangerous** – Can affect existing data or users if misused *** | Setting | What it does (Plain English) | Level | Notes | | ------------- | -------------------------------------------------------- | -------- | ------------------------------- | | Field Name | The name of the information you’re collecting | Beginner | Used to identify the field | | Field Type | The kind of data stored (text, number, date, file, etc.) | Beginner | ⚠ Hard to change later | | Label | The text users see next to the field | Beginner | Can be changed per table | | Required | Makes the field mandatory before saving | Beginner | Use only for essential data | | Help Text | Extra guidance explaining what to enter | Beginner | Improves data quality | | Placeholder | Example text shown inside the field | Beginner | Disappears when typing | | Default Value | Automatically fills a value for new records | Beginner | Saves time for users | | Show in List | Controls whether this appears in table views | Beginner | Turn off for rarely used fields | | Multi‑Select | Allows choosing more than one option | Beginner | Only for suitable field types | | Searchable | Allows filtering and searching by this field | Beginner | Improves usability | \--- \--- ### Advanced settings (optional) You do **not** need these for most use cases. *** | Setting | What it does (Plain English) | Level | Notes | | -------------- | -------------------------------------- | -------- | ---------------------------------------- | | Read‑Only | Users can see but not change the value | Advanced | ⚠ Can confuse users if unexpected | | Unique | Prevents duplicate values | Advanced | ⚠ Can block saves if data already exists | | Minimum Length | Shortest allowed text value | Advanced | Usually safe | | Maximum Length | Longest allowed text value | Advanced | Can truncate input | | Minimum Value | Lowest number allowed | Advanced | For numeric data only | | Maximum Value | Highest number allowed | Advanced | For numeric data only | | Decimal Places | Controls numeric precision | Advanced | Affects how values are stored | | Field Size | Controls how large the field looks | Advanced | Visual only | | Column Span | How wide the field appears | Advanced | Layout only | | Row Span | How tall the field appears | Advanced | Layout only | | Group | Visually groups related fields | Advanced | Improves form clarity | | Label Position | Moves label above, beside, or hides it | Advanced | Affects usability | | Emphasis | Makes the field stand out more | Advanced | Use sparingly | *** ### Conditional behaviour (advanced) These settings create **dynamic forms**. *** | Setting | What it does (Plain English) | Level | Notes | | ----------------------- | ------------------------------------- | -------- | -------------------------- | | Condition Trigger Field | The field that controls this one | Advanced | Must exist first | | Condition Rule | The rule that activates the condition | Advanced | Needs careful testing | | Condition Action | What happens when the rule matches | Advanced | ⚠ Can hide required fields | \--- *** ### File upload settings (advanced) Only applies to file fields. *** | Setting | What it does (Plain English) | Level | Notes | | ------------------ | ------------------------------- | -------- | --------------------------- | | Allowed File Types | Restricts what users can upload | Advanced | Prevents unwanted files | | Maximum File Size | Limits how large uploads can be | Advanced | Too low may frustrate users | *** ### System & formatting settings (use with care) These are **rarely needed**. *** | Setting | What it does (Plain English) | Level | Notes | | ------------------- | -------------------------------------- | -------- | ------------------------- | | Auto‑Increment | Automatically increases the value | Advanced | ⚠ Hard to fix once live | | Next Auto‑Increment | The next number that will be used | Advanced | ⚠ Can cause duplicates | | Format | Controls how values are shown | Advanced | Display only | | Input Prefix | Text shown before the value | Advanced | £, $, etc | | Input Suffix | Text shown after the value | Advanced | %, units | | Input Mask | Forces values into a strict format | Advanced | ⚠ Can prevent valid input | | Storage Mode | Controls how data is stored internally | Advanced | ⚠ Admin‑only setting | | CSS Class | Custom styling hook | Advanced | ⚠ For expert use only | *** ### Recommendation for new users > 💡 **Start simple**\ > Use only Beginner settings at first.\ > Add advanced options only when you know exactly what problem you are solving. *** ### Final tip If you’re not sure whether a setting is safe to change: * Leave it as‑is * Test changes on a copy * Or ask an admin before applying it live --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.objectra.com/documentation/what-is-a-field.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.