Document titles in iVendNext help identify and manage transactions.
Default titles like “QUO-0001” lack context, but adding customer names, dates, or codes makes them clearer and more useful. This article shows how to customize them dynamically.
Default titles like "SINV-2023-001" are functional but lack descriptive value. Custom titles help:
Improve searchability: Quickly identify documents by key attributes (e.g., "PO for ABC Corp – 15-May-2024").
Enhance reporting: Group documents by customer, project, or status.
Reduce errors: Minimize confusion in high-volume workflows (e.g., quotations for the same customer).
From iVendNext 6.0 onwards, all transactions include a 'Title' property. If absent, add a custom field:
Navigate to:
Setup > Customize > Customize Form
Select the form (e.g., Quotation, Sales Invoice).
Add a Text or Read-Only field labeled "Title".
Save the changes.
Use Python-style string formatting to auto-generate titles from document fields.
Edit the Title Field in the form.
In the Default or Options field, enter:
{customer_name} – Quotation #{naming_series}
{customer_name} fetches the linked customer’s name.
{naming_series} pulls the auto-generated ID (e.g., "QUO-0005").
Save and refresh the form.
Result: Titles will display as "ABC Corp – Quotation #QUO-0005".
Editable Titles: Users can modify the default title by clicking the document header.
Fixed Titles: Automatically update when referenced fields change.
To enforce fixed titles, use the Options property with a script or formula.
For complex logic (e.g., titles based on multiple conditions), use Client Scripts:
// Example: Set Quotation title to include status
cur_frm.cscript.refresh = function(doc) {
if (doc.status === 'Approved') {
doc.title = `APPROVED – ${doc.customer_name}`;
}
};
To include data from linked documents (e.g., terms from a Contract):
Add a Link Field (e.g., contract_id).
Reference it in the title:
{contract_id} – {customer_name}
Here’s a quick look at some of the best practices for customizing Document Titles.
Keep Titles Concise: Prioritize key fields (e.g., customer, date, type).
Standardize Formats: Use consistent patterns across DocTypes (e.g., {project_code}_{date}).
Test Thoroughly: Verify titles update correctly when linked fields change.
Here’s a quick look at some common issues you might run into.
Title Not Updating? Check field names for typos (e.g., customer_name vs. customer).
Permission Issues: Ensure users have edit rights to the Title Field.