Choose the Simpro custom fields parsers can fill
The custom fields you tick here are the ones a Simpro parser can send a value to. Ticking a field adds it to the parser's field list as [Custom]: name (Text) and to the field list in a template. Fergus parsers are never offered them, because Fergus has no custom fields.
Before you start
A Simpro credential has to be chosen and saved first. See Simpro credentials. Until then the page stays on its loading spinner.
Step by step
- Open Work Order Import, then Settings, then Simpro Custom Fields.
- Under each Simpro company, tick the fields you want. Each is listed as the field name followed by its type, for example "Gate code: Text".
- Click Save. The page says "Custom fields updated."
The page loads the job custom fields of every company on the Simpro build that is not a template company. A company with no text fields says "No custom fields found." When no company has any, the page says "No Simpro project custom fields available."
Only Text fields are listed. List, Date, Numeric and Hyperlink fields are hidden even though Simpro has them.
The ticked fields are shared by every Simpro parser on the account.
How it maps to Simpro
After the job is created, each custom field the parser read is written to the job with
PATCH /jobs/{jobID}/customFields/{customFieldID}, using the inbox's Simpro company. A Simpro quote
parser writes to /quotes/{quoteID}/customFields/{customFieldID} with the same field ID.
When it goes wrong
A custom field value is missing in Simpro
If Simpro refuses the value, the job is still created and nothing shows on the Dashboard record or in the not processed email. Check the field in Simpro and the text the parser read.
I unticked a field a parser already uses
The parser keeps its rule. A custom field written straight to the job is still sent. A template that
contains {{Custom: name}} is no longer filled in for that field, because the template only knows the
fields ticked here. Tick it again.
The field is from a different company than the inbox
The value is written using the inbox's company. Tick fields from the company the inbox imports into.