Knowledgebase articles
- Welcome to the Knowledge Base
- Introduction
- Training
- Getting Started
- Preferences
- Activities
- Cases
- Importing Data
- Leads
- Marketing
- Introduction to Marketing
- Marketing Campaigns
- Mailing Lists
- Products
- Mailshots
- Upload Library
- Templates
- Event Management
- Compliance Records
- Spotler Integration
- What is Spotler?
- Navigating your Spotler homepage
- GatorMail
- GatorLeads / Web Insights
- Tracking Code
- Setting up the Plugin
- Viewing Web Insights Data on your Form Layouts
- Domain Names and Online Activities
- Reporting incorrect Leads created through Web Insights
- Reporting on Web Insights data
- Using UTM Values
- Why aren’t Online Activities being created in the database?
- Why is GatorLeads recording online activities in a foreign language?
- GatorSurvey
- GatorWorkflow
- GatorPopup
- Opportunities
- Projects
- Integrations
- Mapping
- Electronic Signing Tools
- Creditsafe Integration
- Zapier
- Introduction to Zapier
- Available Triggers and Actions
- Linking your Workbooks Account to Zapier
- Setting up Zaps
- Posted Invoices to Xero Invoices
- Xero payments to Workbooks Tasks
- New Case to Google Drive folder
- New Case to Basecamp Project
- New Workbooks Case to JIRA Ticket
- Jira Issue to new Case
- 123FormBuilder Form Entry to Case
- Eventbrite Attendee to Sales Lead and Task
- Facebook Ad Leads to Sales Leads
- Wufoo Form Entry to Sales Lead
- Posted Credit Note to Task
- QuickBooks Online
- Survey Monkey responses to Tasks
- Multistep Zaps
- Email Integrations
- Email Dropbox
- Workbooks Exchange Server Sync
- Workbooks Outlook Connector
- RevenueGrid Intelligence and Engage
- Event & Webinar Integration Tools
- GoToWebinar
- ON24
- Microsoft Office
- Outreach
- Installation
- Outreach Authentication
- Sync People to Outreach Prospects
- Sync Organisations to Outreach Accounts
- Sync Workbooks Opportunities to Outreach
- Sync Tasks/Activities from Workbooks to Outreach
- Sync Outreach Sequences to Workbooks
- Sync Outreach Sequence States to Workbooks
- Sync Outreach Sequence Step Numbers to Workbooks
- Sync Prospects/Accounts/Opportunities from Outreach to Workbooks
- Sync Outreach Tasks/Calls/Meetings to Workbooks
- Scribe/Workbooks Connector
- RingCentral
- Auditing
- Comments
- People & Organisations
- Reporting
- Introduction to Reporting
- Using Reports
- Introduction to Charts
- Exporting Reports
- Advanced Reporting
- Report Snapshots
- Dashboards
- Transaction Documents
- Introduction to Transaction Documents
- Displaying & Adding Transaction Documents
- Copying Transaction Documents
- Transaction Documents Fields Help
- Transaction Documents Line Items Help
- Printing & Sending Transaction Documents
- Managing Transaction Document Currencies
- Managing Transaction Document Statuses
- Setting a Blank Default Currency on Transaction Documents
- Credit Notes
- Customer Orders
- Invoices
- Quotations
- Supplier Orders
- Contract Management
- Sagelink
- Introduction to Transaction Documents
- Auditing
- Configuration
- Introduction to System Administration
- Users & Security
- Database
- Accounting
- Email & Integration
- Customisation
- Creating & Modifying Picklists
- Theme
- Record Types
- Creating Custom Fields
- Report-based Custom Fields
- Linked Fields & Reference Fields
- Record Templates
- Form Layouts
- Customising relationships between parties
- Opportunity Stages
- Custom Records
- Sign In Customisation
- Automation
- Contact Support
- Releases & Roadmap
Linking Custom Field Values
How to link two Custom Field Values to automatically populate the other when converting or copying documents.
Populating custom fields with the value from a custom field on another record (linking custom field values)
It’s bad practice to give two custom fields on the same record type the same field label as it will cause confusion in reports and filtered grids. However, there are instances when you will want to create custom fields with the same field label (but on different record types) so that the values entered in those fields appear on other records. It’s possible to achieve this but only in specific circumstances. For example:
- When converting a Lead so that values captured on the Lead also appear on one or more of the resulting Person / Organisation /Opportunity record.
- When you want the values you’ve put in custom fields you’ve added to a Product to appear on the Line Items of one or more Transaction records when using that Product.
- When copying Transaction records, if you want the value on, say, an Opportunity to appear on an Order.
For the values to copy through from one record to another you need to create a custom field of exactly the same type and with exactly the same field label on both records. For example, if you created a custom field of type Picklist, to which you give the field label ‘Current Solution’ on a Lead and you wanted the value to appear on the resulting Person record when you convert the Lead, you need to add a custom field of type Picklist with the field label ‘Current Solution’ on a Person record too.
Similarly, if you wanted the value to appear on the resulting Opportunity record you would need to add a custom field of type Picklist with the field label ‘Current Solution’ on an Opportunity record. In each case, the picklist used for the field should be the same.
If you add a custom field to a Product – for example an integer field called ‘Weight’, and you want the weight of the product to be visible on a Line Item when that Product is added to a Transaction, you must create a custom field of type integer on the Line Item for each Transaction record type where you want to be able to see the weight and give it a field label of ‘Weight’.
Finally, if you add a custom field to either the header or the line item of a Transaction record and you want the value to appear on any other type of transaction when you use the Copy Document functionality, you need to add a custom field of the same type and with the same field label to each Transaction record.
NOTE: You can only copy values from custom fields to custom fields and not from custom fields to standard fields or vice versa. The field label and data type must be exactly the same, otherwise the value you want to see will not appear.