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 Set Excluded Role records 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, control the number of records returned, and customize the output by including human-readable labels for picklist and reference fields. This operation is useful for scenarios where detailed and specific data about excluded roles in contract exclusion sets is needed, such as auditing, reporting, or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching records or limit the results to a specified maximum number. |
| 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 with Autotask API query criteria to filter the records returned. |
| Add Picklist Labels | Indicates whether to automatically add '_label' fields for picklist fields to provide human-readable values. |
| Add Reference Labels | Indicates whether to automatically add '_label' fields for reference fields to provide human-readable values. |
| 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 whether user-defined fields (UDFs) are brought to the top level of each object instead of being nested. |
Output
JSON
id- Unique identifier of the Contract Exclusion Set Excluded Role record.fieldName- Various fields representing the properties of the excluded role as returned by the Autotask API.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields*- User-defined fields nested or flattened depending on the 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is correctly formatted and follows Autotask API query criteria.
- Requesting more than 500 records when 'Get All' is false will be limited to 500 due to API constraints.
- If no records are returned, verify that the filter criteria match existing data.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size and processing time.
- Incorrect field names in 'Select Columns' or filter criteria may cause errors or empty results; use 'Get Field Info' to confirm exact field names.
Links
- Autotask API Basic Query Calls - Official Autotask documentation for constructing advanced filter queries.