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 Sets from the Autotask REST API using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the results according to their needs. This is useful for scenarios where you need to extract specific subsets of contract exclusion sets based on detailed conditions, such as filtering by certain attributes or relationships. For example, a user might want to get all contract exclusion sets that exclude specific roles or billing codes, or that meet custom criteria defined in the advanced filter.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching contract exclusion sets or limit the number of results. |
| Max Records | Specifies the maximum number of contract exclusion sets to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter the contract exclusion sets. This allows for complex and precise querying. |
| Add Picklist Labels | If enabled, adds human-readable '_label' fields for picklist fields in the output, making the data easier to understand. |
| Add Reference Labels | If enabled, adds 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 no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract exclusion set.name- Name of the contract exclusion set.description- Description of the contract exclusion set.excludedRoles- List of roles excluded by this contract exclusion set.excludedBillingCodes- List of billing codes excluded by this contract exclusion set.userDefinedFields- Array of user-defined fields associated with the contract exclusion set, unless flattened._label- Human-readable labels for picklist and reference fields if enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property can cause errors. Ensure the JSON string is well-formed and follows the Autotask API query criteria format.
- If no results are returned, verify that the filter criteria match existing contract exclusion sets.
- Setting 'Max Records' outside the allowed range (1-500) will cause validation errors.
- If picklist or reference labels are not appearing, ensure the corresponding options are enabled and that the fields have non-empty values.
- API rate limits or authentication errors may occur if the API key is invalid or lacks necessary permissions.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask API.