Custom fields allow businesses to extend standard forms in iVendNext to capture unique data requirements. Whether you need to track additional customer details, add project-specific fields, or customize inventory attributes, creating custom fields ensures your system adapts to your workflow—not the other way around.
This guide provides a step-by-step approach to adding, configuring, and managing custom fields in iVendNext.
Navigate to:
Home → Customization → Form Customization → Custom Field
(or)
Open any DocType list view (e.g., Customer, Item) → Click Customize in the sidebar.
Click Add Row in the Custom Field table.
Fill in the following details:
Document: Select the target DocType (e.g., "Customer").
Label: Name your field (e.g., "Loyalty Tier").
Field Type: Choose a type (e.g., Select, Link, Date).
Options: Required for Select fields (enter values separated by new lines).
Fetch From: For Link fields, specify the linked DocType (e.g., "Project").
Click Update to save.
Example:
Field Type: Select
Options:
Bronze
Silver
Gold
Set a pre-filled value (e.g., default "Country" = "USA").
Use {field_name} syntax to reference other fields (e.g., {customer_name}'s Order).
Show/hide fields conditionally (e.g., display "VIP Discount" only if "Is VIP" is checked).
Syntax: depends_on = "field_name"
Permission Level: Restrict editing to specific roles (e.g., "Accounts Manager").
Hidden: Hide fields from view (useful for backend calculations).
In List View: Display the field in DocType list views.
Issue: Cannot change from Data to Link after creation.
Solution:
Go to Custom Field list (via search bar).
Open the field record → Modify Field Type and Options.
Save and refresh.
Use Case: Assign tasks to multiple users.
Steps:
Create a child DocType (enable Is Child Table).
Add a Table MultiSelect field in the parent DocType.
Link to the child DocType in Options.
Combine multiple fields into a title (e.g., {customer_name} - {invoice_date}).
Prefix custom fields with custom_ (e.g., custom_loyalty_tier) to avoid conflicts.
Use Rename Fieldname in the Custom Field list to modify existing fields.
Avoid exceeding MySQL’s row size limit (65,535 bytes):
Convert Data fields to Text/Long Text where possible.
Reduce Length property for VARCHAR fields (default: 140).
Test fields in staging before deploying to production.
Use Mandatory and Unique flags to enforce data integrity.
Custom fields empower businesses to tailor iVendNext to their unique needs. By following this guide, you can:
✔ Add new fields without coding.
✔ Configure dependencies and defaults.
✔ Resolve common issues like datatype changes.