Fields in iVendNext shape how data is entered, shown, and used across forms and documents. Choosing the right type—whether for sales, inventory, or customer records—boosts accuracy and efficiency. This guide covers field types, their uses, and tips for applying them effectively.
Purpose: Connects to another master document (e.g., Customer, Item, Supplier).
Example: In a Quotation, the "Customer" field links to the Customer Master.
Key Features:
Auto-completes entries based on linked data.
Ensures data consistency by referencing a single source.
Purpose: References multiple document types dynamically.
Example: In an Opportunity, a Dynamic Link can point to either a Lead or a Customer.
Key Features:
Adapts based on the selected document type.
Reduces the need for multiple link fields.
Purpose: Provides a dropdown list of predefined options.
Example: A "Status" field with options like Draft, Submitted, Cancelled.
Key Features:
Ensures standardized data entry.
Options can be modified in the Customize Form settings.
Purpose: Embeds a child table within a document.
Example: The "Items" table in a Sales Order links to Sales Order Items.
Key Features:
Supports multiple rows of structured data.
Can be configured as editable grids.
Purpose: Captures geographic data (points, lines, polygons).
Use Case: Tracking land boundaries in the Agriculture module.
Key Features:
Supports GeoJSON format.
Interactive map interface for plotting locations.
Purpose: Captures electronic signatures for approvals.
Use Case: Signing contracts, invoices, or delivery receipts.
Key Features:
Supports freehand drawing.
Stores signatures securely in the database.
Purpose: Allows multiple selections from a linked document.
Use Case: Assigning a ToDo task to multiple users.
Key Features:
Functions like a Link + Table field.
Prevents duplicate selections.
Here’s a quick look at some of the best practices for using Field Types.
Use Link Fields for master data (Customers, Items) to ensure consistency.
Apply Select Fields for standardized choices (e.g., Status, Priority).
Group related fields using Section Breaks and Column Breaks.
Set default values for frequently used fields (e.g., default date = today).
Limit the number of fields per form to prevent slowdowns.
Use Text/Long Text fields for large data instead of multiple small fields.