Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
The 'Get Many (Advanced)' operation for the 'Product Vendor' resource in the Autotask node allows users to retrieve multiple product vendor records using advanced filtering criteria. This operation is beneficial when you need to query product vendors with specific conditions beyond simple retrieval, such as filtering by custom fields or complex query parameters. For example, you can fetch all product vendors that meet certain business criteria defined in a JSON filter, control the number of records returned, and customize the output with additional labels and field selections.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching product vendor records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of product vendor records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array with Autotask API query criteria to filter the product vendor records. This allows complex and precise querying based on Autotask's REST API filtering capabilities. |
| Add Picklist Labels | Indicates whether to automatically add human-readable '_label' fields for picklist fields in the output. Labels are added only for non-empty values. |
| Add Reference Labels | Indicates whether to automatically add human-readable '_label' fields for reference fields in the output. Labels are added only for non-empty values. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) should be brought up to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the product vendor record.name- Name of the product vendor.otherFields- Additional fields returned based on selected columns or all fields if none selected._label- Human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication.
- Relies on the Autotask REST API to perform advanced filtered queries.
Troubleshooting
- Ensure the 'Advanced Filter' JSON string is correctly formatted and contains a valid 'filter' array as per Autotask API documentation.
- If no records are returned, verify that the filter criteria match existing product vendor records.
- When 'Get All' is false, check that 'Max Records' is set within the allowed range (1-500).
- If picklist or reference labels are not appearing, confirm that the respective 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
- Errors related to authentication usually indicate invalid or missing API credentials; verify the Autotask API key configuration.
- If user-defined fields are not accessible as expected, check the 'Flatten User-Defined Fields' option to control their structure in the output.
Links
- Autotask API Basic Query Calls - Official Autotask documentation for constructing advanced query filters used in the 'Advanced Filter' property.