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
This node operation retrieves multiple Contract Exclusion Billing Code records from the Autotask system using an advanced JSON filter. It is useful for users who need to query and extract specific billing code exclusions based on complex criteria, such as filtering by multiple fields or conditions. For example, a user can fetch all exclusion billing codes that match certain contract parameters or statuses by providing a custom JSON filter.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching records or limit the number of results. |
| Max Records | Specifies the maximum number of 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 that defines the query criteria according to the Autotask API's advanced query syntax. This allows complex filtering of records based on multiple conditions. |
| Add Picklist Labels | Whether to add human-readable label fields for picklist fields in the output, enhancing readability. |
| Add Reference Labels | Whether to add human-readable label fields for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Determines if user-defined fields (UDFs) should be moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Contract Exclusion Billing Code record.fieldName- Various fields of the Contract Exclusion Billing Code as returned by the Autotask API, depending on selected columns and filters.
_label - Human-readable labels for picklist or reference fields if enabled.userDefinedFields- User-defined fields either nested or flattened to top-level depending on the flattenUdfs option.
Dependencies
- Requires an Autotask API credential for authentication to access the Autotask REST API.
Troubleshooting
- Ensure the 'Advanced Filter' JSON string is correctly formatted and follows the Autotask API query syntax; invalid JSON or incorrect filter structure will cause errors.
- If no records are returned, verify that the filter criteria match existing data and that the 'Get All' and 'Max Records' settings are appropriate.
- If picklist or reference labels are not appearing, check that the corresponding options 'Add Picklist Labels' and 'Add Reference Labels' are enabled.
- API rate limits or authentication errors may occur if the Autotask API credentials are invalid or expired; verify and update credentials as needed.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.