YESDINO gives you the ability to plug in a broad spectrum of custom fields that can be attached to any record type – from simple text labels to complex geo‑coordinates, from single‑select dropdowns to auto‑calculating formulas. In practice you can add up to 200 custom fields per entity, covering everything from basic data points like "Customer Name" to niche attributes such as "Warehouse Latitude". For a complete overview, check out the official YESDINO documentation.
Core Custom Field Categories
YESDINO groups its field types into primary buckets, each with distinct storage limits, formatting rules, and typical use‑case scenarios. The platform supports 30+ distinct field types, but most implementations revolve around a core set shown in the table below. Understanding these categories helps administrators design data models that balance flexibility with performance, ensuring that your workspace remains responsive even as datasets grow to thousands of records.
| Field Type | Subtype / Format | Maximum Length / Precision | Common Use Cases |
|---|---|---|---|
| Text | Single‑line | 255 characters | Name, email, short description |
| Text | Multi‑line | 5,000 characters | Comments, notes, long instructions |
| Number | Integer | 10 digits | Quantity, ID, counter |
| Number | Decimal | 2 decimal places | Price, weight, percentage |
| Dropdown | Single‑select | Up to 50 options | Status, category, priority |
| Dropdown | Multi‑select | Up to 100 options | Tags, features, capabilities |
| Date / Time | Date only | ISO 8601 (YYYY‑MM‑DD) | Start date, deadline |
| Date / Time | Date and Time | ISO 8601 with timezone | Created at, scheduled event |
| Boolean | Checkbox / Toggle | True / False | Active status, agreement acceptance |
| Currency | Fixed decimal | 2 decimal places + symbol | Invoice amount, budget allocation |
| URL | Web link | 2,083 characters | Reference links, documentation |
| Attachment | File upload | Up to 10 MB per file | Contracts, images, reports |
| Formula | Auto‑calculating | Depends on inputs | Total price, age calculation, tax |
| Relation | Link to another record | Up to 10 linked records | Parent account, related contacts |
Detailed Field Type Explanations
When selecting the appropriate field type for your data, consider not only the current requirements but also potential future scalability. The Text field, for instance, is the workhorse of most custom field implementations. Single‑line text fields are optimized for quick lookups and searches, making them ideal for identifiers like customer codes, product SKUs, or unique reference numbers. Multi‑line text fields, on the other hand, support longer-form content and are perfect for capturing detailed notes, meeting minutes, or comprehensive descriptions that might exceed the scope of a quick memo.
Practical Implementation Examples
For a typical sales pipeline setup, you might configure a multi‑line text field called "Sales Notes" to allow your team to document conversation highlights and customer concerns during calls. Meanwhile, a single‑line text field labeled "Deal ID" can serve as a quick reference identifier that sales reps can search for instantly when following up on active negotiations. The distinction between these two text subtypes becomes particularly important when your workspace contains thousands of records, as single‑line fields index faster and consume less storage overhead.
Number fields deserve careful attention during the configuration phase, as the choice between integer and decimal representation affects both storage efficiency and calculation accuracy. If your use case involves tracking quantities in a warehouse where fractional units make no sense, integer fields provide the right level of precision while maintaining optimal performance. For financial data such as pricing, discounts, or tax calculations, decimal fields with two decimal places ensure that monetary values remain accurate to the cent, preventing rounding errors that could compound across large transaction volumes.
Dropdown Configuration Best Practices
Dropdown fields represent one of the most powerful tools for standardizing data entry across your organization. When configuring single‑select dropdowns for fields like "Pipeline Stage" or "Account Type", take time to define the option list during the initial setup phase, as frequent additions or modifications to dropdown options can affect historical reporting consistency. Single‑select dropdowns are limited to 50 options, which covers the vast majority of categorical use cases, from simple binary choices like "Hot / Warm / Cold" to more granular classifications like regional offices or product lines.
Multi‑select dropdowns extend this capability by allowing records to belong to multiple categories simultaneously, making them ideal for tagging systems. For example, a "Service Tags" field might allow users to select multiple capabilities such as "Cloud Hosting", "Managed Security", and "24/7 Support" for a single customer account. With support for up to 100 options per multi‑select field, you can accommodate complex feature matrices without resorting to workarounds like multiple single‑select fields.
Date and Time Handling
Date fields in YESDINO adhere to the ISO 8601 standard, ensuring compatibility with global date formats and facilitating integration with external systems. When you need to capture only the calendar date without time information, the date‑only subtype stores values in YYYY‑MM‑DD format, which sorts chronologically in alphabetical order and simplifies report filtering. For timestamp data where the exact moment matters, the date and time subtype includes timezone information, allowing distributed teams to collaborate across different regions without ambiguity about when records were created or modified.
Consider implementing date fields strategically throughout your data model. A "Contract Renewal Date" field helps account managers anticipate upcoming renewals and proactively reach out to customers before expiration. A "Last Contacted" date field enables service teams to enforce follow‑up SLAs and prioritize outreach to customers who have not engaged recently. These temporal markers become invaluable for building automated workflows that trigger notifications or task assignments based on date conditions.
Boolean, Currency, and URL Fields
Boolean fields provide the simplest possible data representation, storing binary states like true/false, yes/no, or active/inactive. They consume minimal storage space and enable fast filtering in list views and reports. Common applications include marking whether a customer has accepted the latest terms of service, flagging accounts that are exempt from certain billing rules, or indicating whether a product feature is currently enabled for a subscription tier.
Currency fields extend the decimal number field by attaching currency symbols and formatting rules appropriate for each supported denomination. When you create a "Deal Value" field set to USD, YESDINO automatically formats display values as "$50,000.00" while storing the raw numeric value for calculations. This dual representation ensures that humans see familiar formatted amounts while formulas and integrations work with clean numeric data.
URL fields validate input to ensure that entries contain properly formatted web addresses, complete with protocol prefixes like "https://". This validation prevents common errors like missing domain extensions or incomplete paths. When storing reference links to product documentation, support articles, or external resources, URL fields make clickable hyperlinks available directly within record detail views, saving users the step of copying and pasting.
Advanced Field Types
Formula fields bring dynamic calculation capabilities directly into your data model, eliminating the need for manual updates when source values change. A "Total Amount" formula field might multiply a "Quantity" integer field by a "Unit Price" currency field, automatically reflecting updated totals whenever either component changes. Formula syntax supports basic arithmetic operations as well as conditional logic, enabling scenarios like calculating customer lifetime value based on subscription tier and account age.
Relation fields create connections between records, establishing the relational aspect of what is fundamentally a hybrid structured database. A "Primary Contact" relation field links a Company record to its designated Contact record, enabling one‑click navigation from account details to responsible individuals. With support for up to ten linked records per relation field, you can model complex relationship networks such as multi‑layered supply chains, hierarchical org structures, or cross‑referenced inventory systems.
Strategic Considerations for Large Deployments
While the platform permits up to 200 custom fields per entity, thoughtful architects balance comprehensiveness against usability. Excessive fields clutter record detail views, increase page load times, and can overwhelm users who must scroll past irrelevant sections. A better approach involves progressive disclosure, where standard fields address the majority of daily workflows while additional fields are organized into collapsible sections or made visible only through custom views.
When planning your field architecture, document the business purpose of each custom field, its expected data volume, and the users who will interact with it most frequently. This documentation proves invaluable during onboarding, audits, and when scaling your implementation across multiple teams or departments. Regular reviews of existing fields to identify rarely used or redundant ones help maintain a lean, efficient data model that grows with your organization rather than becoming an unmanageable accumulation of historical decisions.