Fill AroFlo custom fields from the booking
Custom Fields fills AroFlo custom fields from the booking. Each field is filled on the customer, the site or the task after that record is made, so a booking arrives with its custom fields already set.
Before you start
- Custom Fields is a Business feature. On the Free plan the page says "Custom fields is part of the Business plan.", every control is disabled and Save is off. What you set is kept and used when you move to the Business plan.
- The form needs an AroFlo credential. Without one, reading the fields fails with "Choose an AroFlo credential under Settings first."
- The custom fields have to exist in AroFlo already. Formpiece reads them, it does not make them.
Step by step
- Open your form from Forms. On the Settings tab, open Custom Fields under Written to AroFlo.
- Under Customer, Site and Task, pick a record under Read the fields from. AroFlo only lists custom fields for a record that already exists, so a client, a location and a task each stand in for every new record of that kind.
- Click Add field.
- Under AroFlo custom field, pick the field. The Type column fills in.
- Under Filled from, pick what fills it, then type a value if you picked A fixed value.
- Click Save.
Remove takes a row off. Nothing is written to the form until you click Save, and the dashboard asks before you leave with changes that are not saved.
The three zones
| Section | AroFlo zone | Pick a sample by |
|---|---|---|
| Customer | CLIENTS | Typing at least two characters of the client's name |
| Site | LOCATIONS | Typing part of the address. The list loads when you open it |
| Task | TASKS | Typing the job number, task name or client. The list loads when you open it |
If AroFlo has no record of that kind to pick from, the list says "AroFlo has none to pick from". If you click Add field before picking a sample, Formpiece reads the fields from the account's recent records instead.
A field is offered once. Any field another row already uses is left out of the choices. Archived fields are not offered, and neither are fields that hold documents or drawings, because a booking can't fill those.
What fills a field
Filled from groups the choices by where the answer comes from:
| Group | What it offers |
|---|---|
| Customer field | The customer fields the form asks, under their own labels |
| Site field | The site fields the form asks |
| Task field | The task fields the form asks |
| Question | Each question that is switched on |
| Fixed value | One value you type, written the same on every booking |
A field the customer has not been asked for is not in the list. If a row's source is later turned off on its own page, the row shows "No longer asked on the form" until you pick another.
The Type column shows AroFlo's own type in Formpiece's words: Text, Long text, Number, Date, List, Yes or no, Multiple choice, Web address or Barcode.
Required fields
A field AroFlo marks as required shows a Required in AroFlo tag. The form can't be saved while a required field in a zone you have read is left unmapped. Save stays off and says why beside the button:
- "Save is off: choose the AroFlo field for each row in customer." (or site, or task)
- "Save is off: say what "Field name" is filled from."
- "Save is off: "Field name" is required by AroFlo on a client, so it has to be mapped." (or location, or task)
Existing clients and sites
A booking for a client AroFlo already holds only changes that client's custom fields when Update details when an existing client is found. is ticked on Customer fields. An existing site is treated the same way.
When it goes wrong
The custom fields could not be read
The message under the picker gives the reason. "The AroFlo API could not be reached." means the browser could not get an answer, so try again. "AroFlo did not answer." is what shows when AroFlo gives no reason.
A field I expect isn't in the list
Another row already uses it, it is archived, or it holds documents or drawings. A field that was added in AroFlo after you read the list will show once you pick the sample again.
Save is off
Read the reason beside the button. A row with no AroFlo field, a row with no source, and an unmapped required field each stop a save.