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 updates an existing Contract Role Cost in the Autotask system. It is useful for scenarios where you need to modify details of a specific contract role cost, such as adjusting rates or other attributes associated with a contract role. For example, you might update the cost associated with a particular role in a contract to reflect new pricing or changes in contract terms.
Properties
| Name | Meaning |
|---|---|
| Contract Role Cost ID | The unique identifier of the contract role cost record to update. This is required to specify which contract role cost will be modified. |
| Fields | The set of fields and their new values to update on the contract role cost. This allows specifying which attributes of the contract role cost should be changed and their updated values. |
Output
JSON
id- The ID of the updated contract role cost record.fieldsUpdated- The fields that were updated with their new values.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the Contract Role Cost ID provided exists and is correct; otherwise, the update will fail with a not found error.
- Verify that the fields to update are valid and allowed to be modified; invalid fields may cause errors.
- Check that the API credentials are valid and have sufficient permissions to perform update operations on contract role costs.
- Common error messages include 'Resource not found' if the ID is incorrect, or 'Invalid field' if unsupported fields are provided. Resolving these involves verifying input parameters and credentials.