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 manage records within various SugarCRM modules, including Purchase Line Items. Specifically, for the Purchase Line Item - Delete operation, it deletes a record identified by its unique ID from the SugarCRM system.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or incorrect purchase line items in SugarCRM.
- Integrating with other systems to remove purchase line items when corresponding data is deleted elsewhere.
- Managing CRM data lifecycle by programmatically deleting records based on business rules.
Example use case:
- A workflow that triggers when a purchase order is canceled, automatically deleting associated purchase line items from SugarCRM to keep data consistent.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Purchase Line Item record to delete. This must be provided to specify which record to remove. |
Output
The output JSON contains the response from the SugarCRM API after attempting to delete the specified Purchase Line Item record. Typically, this will confirm successful deletion or provide error details if the operation failed.
No binary data is output by this node.
Dependencies
- Requires an active connection to a SugarCRM instance via an API key credential (an API authentication token).
- The node uses SugarCRM REST API v11_11 endpoints.
- Proper credentials with permissions to delete records in the Purchase Line Item module are necessary.
- Network access to the SugarCRM base URL configured in the credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent ID will result in an error indicating the record could not be found.
- Insufficient permissions in the SugarCRM API credentials may cause authorization errors.
- Network connectivity problems or incorrect base URL configuration can lead to request failures.
Error messages and resolutions:
"No records found or unexpected API response structure": This usually means the ID does not exist or the API returned an unexpected format. Verify the ID and ensure the record exists.- Authorization errors: Check that the API credentials have delete permissions and are correctly configured.
- JSON parsing errors: Ensure the ID property is a valid string and no malformed JSON is passed in related fields.