Implementing Distributed Delete filter action but am running into some snags that have to do with the order in which the DSO actions appear to be running.
Currently we have filters that perform Distributed Transfers. These run in Phase 3. I also perform Distributed Deletes, which also fire in Phase 3 and fire before Distributed Transfers. This is causing errors to get dumped to our arerror log file and is also unecessary work. The Delete portion works so there is no need to do the Transfer. Trying to figure out how to either stop the Transfer or switch the order so that the Transfer happens first and then the Delete. The way a lot of workflow was built is that when a status changes to Delete filters fire to delete the record. In the end the Delete runs so the tables are in sync but hate getting all of the errors in the log file about "Pending distributed operation for this entry canceled due to error (ARDSNOTE 3003)". Thank you. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
