How to Add a New Field

An entity stores all the data your application uses.
A field is a single data point inside that entity - for example: title, description, price, status, or date.

If the app needs to save a new type of information, you must create a field for it.
No field = no place to store that data.

Below is a clear, practical tutorial for adding a new Text field inside the Offers entity.

---

---

Commonly Used Field Types

• Text - Short, single-line text input. Used for names, titles, labels, and similar short content.
• MultiLineText - Longer text with multiple lines. Ideal for descriptions, notes, and comments.
• Integer - Whole number (no decimals). E.g. number of users, quantity, order number.
• Decimal - Number with decimal places. E.g. 3.14, 1.5.
• Money - Monetary value. Similar to Decimal but formatted as currency (e.g. $100.00).
• Lookup - Reference to another record/table – selects a single value from another collection (1:1 relation).
• MultiSelect -Select multiple values from a predefined list of options (e.g. tags, categories).
• LookupArray - Like Lookup, but allows selecting multiple records from another table (1:N relation).
• Checkbox - Boolean value: true/false, yes/no. Displayed as a checkable box.
• DatePicker - Date input only (no time). E.g. birth date, delivery deadline.
• DateTime - Date and time input combined. E.g. event timestamp.
• MediaFile - Upload a single file (image, PDF, video, etc.).
• MediaArray - Upload multiple files at once – a collection of media.
• Email - Email address input with format validation (must contain @).
• PhoneNumber - Phone number input with format validation.

---

Steps Summary:

1. Developer Toolbox

2. Database (example: "Offers")

3. Hover over Entity

4. Click +

5. Field Type: (example: "Text")

6. Display Name: (example: "Offer Title")

7. Field Name: (example: "OfferTitle")

8. Save

---

Steps Explained:

1. Go to Database

From the Developer Toolbox, open Database.

This is the central place where you define the structure of your data - all your entities and their fields. Every screen, form, and workflow in the app relies on what you set up here.

---

2. Find the Offers Entity

In the list of entities, find for example Offers (or any Entity that you have created earlier).

Be minful that all the entities that you have created are in the Custom Tables section. When creating new entities, the following system fields are automatically generated: CreateUser, ModifyUser, CreateDate, ModifyDate, ID, and StatusID. System fields must exist for proper functionality and therefore should NOT be deleted. The same applies to fields and entities under the System Tables category.

An easy way to distinguish system tables from the ones we created is that they start with an underscore ( for example: _Log ).

---

3. Hover Over the Entity and Click +

Hover over the Offers entity name.
Click "+" to create a new field.

---

4. Choose Field type

Choose Text from the dropdown menu in the Field type text box (or some other field depending on what you would like it to be in your workspace)

Why field type matters:

Each field type defines how data is stored, validated, and displayed.
Choosing the right type ensures the app handles the data correctly. You can find a list of commonly used field types at the beginning of this page.

---

5. Enter Display name in the Display name text box

The Display name is what users see in forms, tables, and components.

Example: Offer Title

---

6. Set Field name in the Field name text box

The Field name is the technical identifier used inside the system.

Rules for field names:

• No spaces

• No special characters

• Use CamelCase (capitalize each word)

• Must be unique inside the entity

Example: OfferTitle

Why this matters:

This name is used in filters, functions, relationships, and automation logic. A clean field name prevents errors later.

---

7. Click Save

Press Save to confirm.
The new field is now part of the Offers entity and ready to use.

What you can do now:

• Display it in tables

• Edit it in forms

• Use it in filtering and sorting

• Reference it in processes and automations

• Build UI components around it

---

Final Note

Adding a new field is essential whenever your application needs to store new information.
A well-structured entity with clearly defined fields makes your app easier to scale, maintain, and automate.