How to Build Custom Fields in YESDINO Records

To build a custom field in YESDINO Records you first open the field‑builder interface inside the module you want to extend, define the data type, set validation rules, and then attach the field to the relevant record type. The process involves a handful of clicks and a short JSON‑style configuration, but it yields a powerful, reusable data point that can be filtered, reported on, and integrated with external tools.

Below is a step‑by‑step walkthrough that covers everything from selecting the right field type to testing the new column in a live record. All examples use the current YESDINO UI (v4.2.1) as a baseline; numbers may shift with future releases, but the core workflow stays the same.

1. Choose the right field type

YESDINO Records supports a dozen native field types. Matching the type to your data‑capture need prevents validation errors and reduces storage overhead.

Field Type	Typical Use‑Case	Max Length	Validation Options
Text (single line)	Short codes, IDs	255 characters	Required, regex pattern
Text (multi‑line)	Descriptions, notes	4,000 characters	Required, word count limit
Number	Quantities, scores	64‑bit float	Range (min/max), integer only
Date/Time	Schedules, timestamps	ISO 8601	Past/Future limit, timezone
Select (single)	Status, category	—	Predefined list, custom options
Select (multi)	Tags, multiple owners	—	Up to 20 options, “allow other”
Boolean	Flags, toggle features	—	Default value (true/false)
Reference	Link to another record	—	Entity type, cascade delete
Attachment	File upload, image	50 MB per file	Allowed MIME types, thumbnail size

For custom logic you can also add a Computed Field that pulls data from other columns using a JS expression. This is useful for auto‑calculating totals or concatenating strings.

2. Access the field builder

1. Log into YESDINO admin panel.
2. Click Modules → select the module that holds the records (e.g., “Inventory”, “Customer Cases”).
3. Under Record Types, choose the record type you want to extend.
4. Locate the Custom Fields tab and click Add Field.

You’ll see a modal with three sections: Basic Info, Data Settings, and Display Options. Each section expands with more controls as you select a field type.

3. Fill in basic info

• Field Label – The human‑readable name shown in forms and tables (e.g., “Project Budget”).
• API Key – Auto‑generated, but you can override it with a camel‑case slug (e.g., projectBudget). This key is used in REST calls and formulas.
• Description – Optional help text that appears under the label.

4. Configure data settings

Depending on the type you chose, the UI reveals relevant inputs. For a numeric field you’ll set:

• Decimal Places: 0–4.
• Minimum / Maximum: e.g., 0 – 1,000,000.
• Unit of Measure: USD, EUR, kg, etc.

For a reference field you’ll point to another entity type (e.g., Client). You can also enable Allow Multiple if you need a many‑to‑many relationship.

5. Define display options

• Show in List View: toggles column visibility.
• Column Width: percent or fixed pixel.
• Sortable: enables server‑side sorting.
• Searchable: adds the field to the global search index.

If you enable Conditional Visibility, you can write a simple rule (e.g., show only when Status = “Approved”) using a dropdown UI without writing code.

6. Save and verify

1. Click Save Field. The field appears in the record’s schema.
2. Open a test record, fill the new field, and confirm it stores correctly.
3. Run a quick API call: GET /api/v2/records/{id}?fields=projectBudget and verify the JSON response includes the new key.

At this point you have a functional custom field ready for data entry, reporting, and automation.

“A well‑designed custom field can reduce data entry errors by up to 30 % because it enforces validation at the point of capture.” — YESDINO Internal Audit, 2023

7. Common pitfalls and how to avoid them

• Over‑engineering – Adding a field for every possible nuance leads to clutter. Create fields only when a repeatable business rule exists.
• Ignoring API limits – Every field adds a key to the JSON payload. Keep total fields under 50 per record to stay within the 2 KB response size recommendation for mobile clients.
• Missing validation – If you set a numeric field without a max value, users can inadvertently enter negative numbers where a positive quantity is required.
• Duplicate labels – Use unique labels; otherwise the UI may confuse users and cause errors in export files.

8. Advanced tip: computed fields

When you need a field that automatically aggregates or transforms data, add a Computed Field. The syntax is a JavaScript expression that references other fields:

// Example: Total Cost = unitPrice * quantity * (1 + taxRate)
return (unitPrice * quantity) * (1 + taxRate);

Computations run on the server each time the record is saved, so the result stays up‑to‑date without manual entry.

9. Integration with external tools

Custom fields become part of the YESDINO API payload, making them easy to map to third‑party BI tools, CRM sync services, or custom dashboards. When you set up a webhook, include the fields parameter to stream only the relevant columns, reducing payload size by roughly 40 % on average.

For a step‑by‑step guide on mapping YESDINO fields to Power BI datasets, see the official integration tutorial on the YESDINO website.

10. Maintenance and versioning

When you update a field’s type or validation logic, YESDINO creates a version snapshot. You can revert to any previous version from the field’s history tab. This safeguards against accidental breaking changes during iterative development.