See which parsed values a Fergus parser can write to Fergus
Destination fields is a read-only list for a Fergus parser. It shows where each value the parser can read is written in Fergus, and flags the values Fergus has no field for. The page appears in the left menu of a parser that Imports to Fergus, and doesn't exist for a Simpro parser. It has no Save, because there is nothing to set.
What it lists depends on the parser's Fergus object. A Jobs or Quotes parser gets the job list, and an Enquiries parser gets the enquiry list.
Jobs and Quotes
A Fergus job takes a title, a description, a customer reference, a customer and a site. A Quotes parser makes the same job with its type set to Quote, and puts a draft quote on it.
| Parsed value | Fergus field |
|---|---|
| Order number | Customer reference on the job |
| Project name | Job title |
| Project description | Job description |
| Project notes | A note on the job |
| Site name | The site's name |
| Site address | The site's address, in street, suburb, region and postcode |
| Customer contact | A contact on the customer |
| Site contact | A contact on the site |
| Site contacts (a block of people) | Contacts on the site. The first is the default contact of a new site. |
| Customer contacts (a block of people) | Contacts on the customer |
| Site contact position | The contact's position |
A contact's name is split on the first space into first and last name. Phone, mobile and email become contact items.
A blank title is replaced by "Work order" and the order number, and a blank description by the title. On a Quotes parser the draft quote is only made on a job the import creates. It has the title, the description, and one section called Work order holding the description. It is valid for the number of days set on the inbox, between 7 and 180.
These values have Not available against them:
| Parsed value | Note on the page |
|---|---|
| Date issued | |
| Due date and time | "Add it to the job description with a template instead" |
| Response time | |
| Site contact department | |
| Site contact notes | |
| Cost centre totals | "Only with quotes" |
| Custom fields | "Fergus has no custom fields" |
Above the table a badge reads "7 without a Fergus field", with "Anything this parser reads for these is shown on the dashboard but is not saved to Fergus." A Fergus parser's field pickers don't offer these values. If one does reach the import, it is skipped and listed against the record as a skipped field.
Enquiries
An enquiry is a name, a contact, a description and an address. It is made without a customer or a site.
| Parsed value | Fergus field |
|---|---|
| Customer contact name | Name |
| Customer contact email | |
| Customer contact phone and mobile | Phone number |
| Project description | Description |
| Site address | Address |
An enquiry always gets a name, so the import falls back through what it has. The name falls back to the site contact, then to the first person in a contacts block, then to the site name, then to "Work order" and the order number. The description also carries the order number, the project notes, any site access note in the address, every person listed in a contacts block and the inbox's default notes.
How the import treats a value Fergus has no field for
It is read, shown on the work order's record on the Dashboard as a skipped field, and left out of Fergus. Nothing fails.
When it goes wrong
A value I mapped isn't in Fergus
Check this list. If the value is one of the Not available rows, Fergus has nowhere to put it.
The customer contact isn't the main contact
An enquiry has no site or customer
That is how a Fergus enquiry works. Choose Jobs on Properties when the work order needs a site and a customer on it. The object can't be changed on a saved parser, so that means a new parser.