This operator fails in the following cases:
Delete a single object and set the operation to fail if any child objects (subtree) exist under this object.

This is the operator dataset of a runtime instance:

After the operator runs, it fails and following data displays on the Operation Results tab.

1 (as we only attempted to delete one object).
0 (as we were unable to delete the object).
Specifies an array of ValueMaps with a single object that contains the DN of the object you tried to delete, and the LDAP error message stating why it was not deleted.

The LDAP message indicates that this object has a subtree under it (it is a non-leaf).
Suppose you want to delete three objects within the same operation: two objects do not have subtrees under them in the LDAP tree, and one object has a subtree under it.

In this example, the first and second objects do not have any subtrees under them. The third object in the list has a subtree under it.
Note that you specified to delete the object (and return an error if children exist).
After the operation ran, it failed and the Operation Results page contains the following data:
3 (as we attempted to delete 3 objects)
2 (as we were able to delete only two objects)
Array of ValueMaps with a single object that contains:


The LDAP message indicates that this object has a subtree under it (it is a non-leaf).
Keep in mind that the delete operation searches the entire list of objects to be deleted. If an object fails to be deleted, the operation continues deleting all other objects in the list, but the operation will also fail when it is over.
|
Copyright © 2014 CA.
All rights reserved.
|
|