Skip to main content

ConnectWise Deletion & Provisioning Logic

Updated over a week ago

Overview

This section outlines how the system handles product deletions and subsequent re-provisioning within the ConnectWise integration.

Product Removal and Billing Impact

When a product is removed from a service license, its associated configurations / product mappings are subsequently purged from the integration. To facilitate this, we process the billing details for both provisioned and deprovisioned products during the active billing cycle. Following this cycle, any configurations or data tied to the removed products are permanently deleted.


Re-provisioning Requirements

When re-provisioning a product that was previously removed, it is critical to re-map it using a strictly unique combination of the Agreement and Addition values.

If you reuse a previous or non-unique combination, the system will encounter backend conflicts. Specifically, it may fail to recognize the reprovisioned product as a new, separate license instance. More critically, reusing these values can cause the system to inadvertently merge the new setup with the historical records of the old product, leading to the accidental overwriting or irreversible loss of existing data.

By ensuring the Agreement and Addition combination is entirely unique, you guarantee a clean re-provisioning process, safeguard historical data, and ensure the system can accurately track and manage both the new and old product instances independently.


Soft Deletion Processing

To maintain accurate synchronization, the system automatically audits soft-deleted items twice a day. Please note that it can take up to 24 hours for these status changes to be fully reflected in the console.

Did this answer your question?