DCO customer web service permits removal of a customer with assets

[DCIM_Support]

DCO 7.5 (any diff in DCO 8?)

I believe both deleteCustomer and synchronizeCustomer will permit the removal of a customer that still has assets assigned.  This leaves the asset <-> customer relationship in an unknown state which mandates the calling program having to check for existing customer assets before delete/synch.

Any plans to adjust this behaviour?

Would it be possible to throw an exception for any cust delete activity that attempts to remove a customer with existing assets?

Happy to raise feature request

(CID:106209245)

[DCIM_Support · Accepted solution]

Hi Ed Tarento This is by design.

The deleteCustomer and syncrhronizeCustomer will allow deletion of customers even if they are assigned to equipment. Upon deletion a reference with the "customer identifier" is kept with the equipment. This is kept in case you deleted the customer by mistake - in which case you simply add the customer with the identifier again - and all relationships between the customer and the equipment is restored.

From a DCO point of view the equipment is in a known state - and basically can be used for other customers without any issues. (and at the same time it allows for automatic re-assignment in case of an accidental removal)

We build this for automation purposes and to allow for automatic deletion of customers with out having a human to manually start the application and remove all references to the particular customer and e.g. a row of racks in case they had terminated their contract.

Best Regards

   Anders

(CID:106209277)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.