When your QuickBase table contains more than 150 fields, not all fields will be retrieved by Workato for performance optimization. For cases whereby your selected QuickBase table has massive, multi-layered tables and contains more than 150 fields, you would need to specify which fields you're interested in using in your recipe.
In this article, we'll talk about the input field list, which is applicable for QuickBase actions. A largely similar concept for the QuickBase connector, the output field list, is covered in this other article, and is applicable for QuickBase triggers.
Input Field List
Fetching only fields that you're interested in.
With Input field list, only fields that are specified in this section will appear subsequently as input fields. Composite fields will also be included when using the top-level name.
- When specifying fields, only provide one field name per line. Field names are case sensitive, hence ensure that field names provided are an exact match as the QuickBase field names.
- Any required fields in your QuickBase table should be displayed in the action by default. Required fields will not show up automatically if you fail to define them in the Input field list.
- Always refresh your recipe schema after changing the Input field list.
- There should NOT be additional spaces in front of or behind each field name
I have a QuickBase table, Event App, with more than 150 fields configured.
When I select the Event App and the Event Attendee Manager table as the table I wish to work with in Workato (for the Add record action), a set of 150 fields would be fetched automatically, with the required fields First Name and Last Name showing up by default.
If the field I'm interested in writing to isn't available in the field selector that enables me to add or remove optional fields, then I would need to explicitly specify the full list of fields I want to show up. For the QuickBase Add record action, the list of fields should include all required fields, otherwise the action will fail as no value would then be provided for all the required fields. Every time you change the input list field, you will need to do a schema refresh so as to reload the new input fields.
Example: I have to explicitly define the required fields as well for Add record action as they won't show up otherwise
Composite fields are essentially fields which may have multiple other fields that make it up - such as an address type field. In such cases, simply providing the main field name as an input will ensure that the multiple other fields that it comprises will be handled properly.
For example, if I would also like to pull out a field "Home Address", which is an address type field, I'll simply put in the field name "Home Address" and the composite fields "Street 1", Street 2", "City", etc. will show up as generated input fields. Again, remember to refresh your schema after changing the input field list!