In short, we are concerned with data integrity in regards to the looping of data. DSO is used to send data from Server A to Server B and back. This involves greater concerns with looping. We would like to take out more of the DSO and integrate workflow to track these forms.

Through workflow, my understanding is that a PUSH field needs to be properly utilized to make sure that every in and out-bound forms can be properly identified.

1)Push fields based on what criteria (identifying with no looping issues)?
2)This prevents duplication how?

Any input at all would be great.

If I understand your concerns correctly, DSO has a loop detection mechanism of itself, and it prevents DSO events to the originating form if not overridden.

The criteria would be whatever you want your records to be unique for, i.e. it depends on your application.

Using the push fields requires user login and in case of update write licenses on both servers.