Hello everyone:
We've run into a very weird problem with DSO and I was hoping maybe someone's encountered this before. We have DSO set up between two identical servers. One server is in Florida, the other is in Ohio. What we do is create a request on the server in Florida. The technicians in Florida work the issue as best they can. If they can't resolve the issue, they DSO it to the tech support center in Ohio. The Ohio techs then work the issue, and when it's solved, they return it back to Florida. Now, when Ohio sends the ticket back, we have workflow on the Ohio server that sets the status of the ticket to Closed. When the Florida server gets ownership of the ticket back, we have a filter that sets the ticket to Group Assigned. The reason for that is, as far as Ohio is concerned, the issue is complete. For Florida, however, the local technicians still need to follow up with the customer, so the ticket is appropriately set to Group Assigned. Here's the problem. That filter I just described? It's evaluated TWICE. The filter's RUN IF qualification is 'TR.Master Flag' = "Yes" AND 'DB.Master Flag' != "Yes". We looked at the SQL log, and what it's doing is... 1. Delete the corresponding row on the Florida server. 2. Insert the corresponding row from the Ohio server with the correct status (Group Assigned). 3. Delete the row. 4. Insert the row with the status set to CLOSED! What the...?! Any ideas? Norm _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
