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 Configuration Item Category UDF (User Defined Field) Association in the Autotask system. It is useful for modifying the mapping of custom fields associated with configuration item categories, allowing users to keep their configuration item metadata up to date. For example, if a user needs to change which custom fields are linked to a specific configuration item category, this node facilitates that update.
Properties
| Name | Meaning |
|---|---|
| Configuration Item Category UDF Association ID | The unique identifier of the configuration item category UDF association to update. This specifies which association record will be modified. |
| Fields | Defines the mapping of fields to update in the association. This property allows specifying which fields and values should be changed in the UDF association. |
Output
JSON
id- The ID of the updated configuration item category UDF association.fieldsToMap- The updated mapping of fields in the association, reflecting the changes made.
Dependencies
- Requires an Autotask API credential for authentication to perform the update operation.
Troubleshooting
- Ensure the provided Configuration Item Category UDF Association ID is valid and exists; otherwise, the update will fail with a not found error.
- Verify that the fields specified in the 'Fields' property are valid and correctly mapped; invalid field names or values may cause the API to reject the update.
- Check that the Autotask API credentials are correctly configured and have sufficient permissions to update configuration item category UDF associations.
- Common error messages include authorization errors (due to invalid credentials), validation errors (due to incorrect field mappings), and not found errors (due to invalid association ID). Resolving these involves verifying credentials, input data, and resource existence.