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 'Contract Exclusion Billing Code' resource with the 'Get Many' operation allows users to retrieve multiple contract exclusion billing code records from the Autotask system. This operation is useful for scenarios where you need to list or analyze multiple exclusion billing codes associated with contracts, such as generating reports, syncing data with other systems, or filtering billing codes based on specific criteria.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields to map and retrieve for the contract exclusion billing codes. Users can specify fields explicitly or use resource mapping to select relevant fields. |
| Get All | Determines whether to return all matching records or limit the number of records returned. |
| Max Records | Specifies the maximum number of contract exclusion billing code records to return when 'Get All' is false. The value can range from 1 to 500. |
| Add Picklist Labels | Indicates whether to automatically add human-readable '_label' fields for picklist fields in the returned data. |
| Add Reference Labels | Indicates whether to automatically add human-readable '_label' fields for reference fields in the returned data. |
| 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 | Determines whether user-defined fields (UDFs) should be brought up to the top level of each returned object instead of being nested. |
Output
JSON
id- Unique identifier of the contract exclusion billing code record.fields*- Various fields of the contract exclusion billing code as specified by the selected fields or default fields.*_label- Human-readable labels for picklist or reference fields, if enabled.
userDefinedFields*- Individual user-defined field entries.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the contract exclusion billing codes exist and that the API credentials have sufficient permissions.
- If the node returns an error about unsupported resource or operation, ensure that the resource is set to 'contractExclusionBillingCode' and operation to 'getMany'.
- When selecting fields, if an invalid field ID is specified, the API may return an error or omit that field from the response.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to retrieve all records.
- Network or authentication errors may occur if the API key is invalid or the Autotask service is unreachable.