Actions40
- Account Actions
- Contact Actions
- Meter Actions
- Opportunity Actions
- Other Actions
- Purchase Line Item Actions
- Revenue Line Item Actions
- Website Registration Actions
Overview
This node integrates with the SugarCRM API to perform various operations on SugarCRM records. Specifically, for the Purchase Line Item resource and the Update operation, it updates an existing purchase line item record in SugarCRM by its ID.
Typical use cases include:
- Modifying details of a purchase line item after it has been created, such as updating its name or description.
- Automating updates to purchase line items based on external triggers or workflows.
- Enriching purchase line item data dynamically during business process automation.
For example, you might update the description or other custom fields of a purchase line item when a related order status changes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the purchase line item record to update. |
| Additional Fields | Optional fields to update on the purchase line item. Includes: |
| - Name: The name of the purchase line item. | |
| - Description: A textual description of the purchase line item. | |
| Custom JSON Payload | A JSON object allowing you to specify additional or custom fields to include in the update. |
| Send JSON Body | Boolean flag indicating whether to send a custom JSON body with the request. |
| JSON Body | The actual JSON content to send if "Send JSON Body" is enabled; can override other fields. |
Output
The node outputs the updated purchase line item record as a JSON object in the json output field. This object reflects the state of the record after the update operation, including any fields that were changed or returned by the SugarCRM API.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a SugarCRM instance via its REST API.
- Needs an API authentication token (OAuth2 password grant) configured through credentials containing base URL, client ID, client secret, username, and password.
- The node uses the SugarCRM REST API version
v11_11.
Troubleshooting
Common issues:
- Invalid or missing record ID will cause the update to fail.
- Incorrect or insufficient permissions on the SugarCRM API user may result in authorization errors.
- Malformed JSON in the "Custom JSON Payload" or "JSON Body" fields can cause parsing errors.
- Network connectivity issues or incorrect base URL configuration can prevent API calls.
Error messages:
"No records found or unexpected API response structure": May occur if the API returns no data or an unexpected format.- Authentication errors typically indicate invalid credentials or expired tokens.
- JSON parsing errors suggest invalid JSON syntax in input fields.
Resolutions:
- Verify the record ID exists in SugarCRM before attempting update.
- Ensure API credentials are correct and have necessary permissions.
- Validate JSON payloads using a JSON validator before input.
- Check network access and base URL correctness.