Autotask icon

Autotask

Interact with Kaseya's Autotask PSA REST API to manage companies, tickets, contracts, and more.

Actions524

Configuration Item Billing Product Association → Update

AI-generated

Overview

This node operation updates an existing Configuration Item Billing Product Association in the Autotask PSA system. It is useful for scenarios where you need to modify the details of a billing product association linked to a configuration item, such as updating billing information or association attributes. For example, you might update the billing product association ID to reflect changes in billing products or correct data.

Use Case Examples

  1. Update the billing product association for a configuration item by specifying the association ID and the fields to update.
  2. Use the dry run option to preview the update request without making actual changes.

Properties

Name Meaning
Billing Product Association ID The ID of the billing product association to update, retrieve, or delete. This is required to identify which association to update.
Dry Run Whether to return a request preview instead of executing the operation. Useful for testing and validation. When enabled, no API call is made and no changes are made to Autotask.
Fields The fields to map and update in the billing product association. This property supports defining the fields to update and supports auto-mapping of fields.

Output

JSON

  • id - The ID of the updated billing product association.
  • fieldsUpdated - Details of the fields that were updated in the association.
  • status - The status of the update operation, e.g., success or failure.

Dependencies

  • An API key credential for Autotask PSA REST API authentication.

Troubleshooting

  • Ensure the Billing Product Association ID is correct and exists in the system to avoid 'not found' errors.
  • If using Dry Run, remember no actual update will occur; use it only for validation.
  • Check API credentials and permissions if the update operation fails due to authorization issues.
  • Handle errors gracefully by enabling 'continue on fail' to capture error messages per item.

Links

Discussion