Builder

Custom fields and entities, shaped to your process

Add an entity, add a field, choose the type — no code, no migrations.

  • Create custom entities and fields in minutes, right in the interface — no code, no config files.
  • Choose from text, number, date, relation to another entity, file and more — each field validates itself.
  • Data is available immediately in pages, reports and automations — no migration, no restart.

Custom field types and the validation each one applies

Every field has a type, and the type decides what can be entered and how the value appears in lists and forms:

  • Short text, long text and formatted text, with a minimum and maximum length and, when needed, a required format — a postcode or a number plate, for example.
  • Whole number and decimal, with a minimum and maximum value, which can also be shown as a progress bar or a rating.
  • Date and date with time; yes or no, which can appear as a toggle.
  • Email, phone and web address.
  • Single and multiple choice, with a colour per option — and, on a status field, the allowed transitions: from “quote” you can only move to “approved” or “declined”.
  • Link to a record of another entity, many-to-many link, and team user.
  • File — a photo, a PDF, a floor plan — and JSON for structured data.

How to create a new entity without coding, step by step

In the builder, a new entity is ready to use in a few minutes — and every step can be revisited later.

  1. 1

    Inside the module, create the entity and give it the name your team uses: “Property”, “Vehicle”, “Member”.

  2. 2

    Add the fields one by one, each with its type and rules: required, unique — two records never repeat the same tax number —, encrypted, or calculated by a formula from other fields of the record.

  3. 3

    Connect it to the rest of the system with links — the vehicle to the customer, the property to its owner — and choose which details of the linked record appear alongside.

  4. 4

    Lay out the form by dragging the fields onto a twelve-column grid.

  5. 5

    Grant access: for each role, decide who reads, creates, edits or deletes — and, field by field, who sees and who edits.

  • Each entity holds up to 100 fields of its own; many-to-many links don’t count towards that limit.
  • Once a field holds data, its type only changes when nothing is lost — from short text to long text, for example.

Custom entity and field examples by industry

At a real estate agency, the Property entity has price, type, area, status and photos, and links to the owner and to viewings. At a car repair shop, the Vehicle keeps the number plate as a unique field and links to the customer and to every repair order.

At an association, each Member gets an automatic number and links to the dues of every year; at a school or training centre, Students and Classes are joined by a many-to-many link. At a clinic, the most sensitive fields of a patient record can be visible only to those providing care.

The fields you create immediately serve automation rules, workflows and everyday work: they appear in lists, filters, boards and charts.

Common questions about custom fields

In Megorix, any new field is created right in the interface — pick the type, give it a name, and it's available immediately, with no code and no database migration.

Yes — Megorix's entity and field builder lets you shape the data structure to your specific process, instead of forcing your business into a fixed template.

In Megorix, creating a new entity is a visual process — no support ticket, no waiting on development.

Up to 100 fields per entity, plus many-to-many links, which don’t count towards that limit. The number of entities you can create depends on your plan.

Only when no value is lost: from short text to long text, for example, or to a choice whose options include every value already stored. In other cases, Megorix refuses the change.

Yes. For each role, field by field, you decide who sees and who edits. A hidden field never reaches anyone who isn’t allowed to see it — not in lists, not through the API, not through the AI.

Yes. A calculated field uses other fields of the same record, with arithmetic, comparisons and functions such as round, max, min or joining text. It does not add up values from other records.

Ready to shape Megorix around your business?

Request a demo