ALERT: Datto Drive Cloud service will no longer be available as of July 1, 2019. For more information, see our end-of-life article. If you'd like to migrate your data to Datto Workplace, see our migration guide.
To learn how to download your Datto Drive Cloud data, please visit this article.

Datto Autotask PSA: Can not SWAP Configuration item, the Serial number already exists in the inventory



I can not swap the Configuration item, and the Serial number already exists in the inventory.

When you try to swap a Configuration Item, you receive the error message, "The serial number ... already exists for this product. All serial numbers must be unique per product."


  • Datto Autotask PSA


Verify if the Inventory already contains that Serial Number, and examine the original Ticket, itself.

  • In some cases, the customer cancels the delivery, and unpicks the Charge, before attempting the Swap of the Configuration item.

When the Configuration Item is generated through a Ticket Charge with a serialized Product, the Serial Number has to be picked, shipped, and added to the Configuration Item, as well.

  • If you are Cancelling the Shipment of the Charge, then unpicking the Item, the Serial number is placed back to the Inventory.
  • If you are trying to Swap the Configuration Item and attempt to receive the Serial number back to the system, this won't be successful. The Inventory already contains the number, after the Charge has been unpicked and/or Deleted.
  • If the Serial Number is NOT in the inventory, check Transfers & Updates. If the Serial number was delivered / Shipped through the Purchase order, it would create a historical record here. You can then Manually, or through an integration, create the CI with the same serial number.

This CI is not linked to the charge, which means you are not able to swap it back into the Inventory. You will have to edit the Serial Number (such as putting an * at the beginning) to allow the swap.

Serial Numbers are NOT required to be unique on the CIs, even with the same product because of the way that some integrations create new CIs when moving Item between customers.

The old CI in inactivated and the new one is created. Swapping the CI back into inventory, however, creates a record in the Transfers & Updates preventing the duplicate record.


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Community Forum or get live help.