Re: DSO Return Filter
DSO needs the mapping with same name to be present on server B which was used to transfer record from server A. Where DSO transfers data with ownership on destination server it also fills a special field from mapping on the transferred record.This field will be later used in DSO update/return operation to get the DSO mapping name. By the way, you don't need to configure DSO return filter to get the updated values back from master destination record to source record. System automatically takes care of updating the values back to source when you modify destination master record. No need to write an explicit filter for this. You only need to make sure you have the mapping existing on the destination server which DSO can use to do the DSO update. DSO return operation can be used to return the ownership back to the source record. Hope this helps On Fri, Apr 12, 2013 at 10:39 AM, Nathan Brandt nathanrbra...@gmail.comwrote: ** Was trying out Return Operation with DSO. I have a Server A and Server B. Server A is sort of Source. I did DSO Mapping and was able to move data from A-Form1 to B-Form1 in Data + Ownership Mode. When TRANSFER is done, as expected, for the record in question, Server B is has Master Flag set to YES. Now If I delete this record from Server B, it automatically gets deleted From Server A. So far so good. But If I modify the record on Server B, changes are not coming back to Server A, so I guess Return operation is not working correctly. Interestingly Filter which I have written for B-Form1, does not ask for DSO Mapping moment you choose Action-DSO-Type (Return). I am wondering how Server B figures out what mapping is to be used for Return Operation and how to make Return operation work? Enabling Filter Logs on Server B shows this error USER: Distributed Server Overlay-Group: 1 Note: Distributed Server cannot transfer or return unless overridden Log file for DSO reveals nothing. ~ Nathan _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: DSO Return Filter
Hi, Actually I figured out the issue, there was some mistake in the return mapping and now it is working fine. As you said about from mapping, I just checked it, this field doesn't get added if you add only Basic distributed fields but if with this, one doesn't have to write return mapping, it would be great. ~ Nathan On Fri, Apr 12, 2013 at 5:54 PM, Rajendra Kapale rajendra...@gmail.comwrote: ** DSO needs the mapping with same name to be present on server B which was used to transfer record from server A. Where DSO transfers data with ownership on destination server it also fills a special field from mapping on the transferred record.This field will be later used in DSO update/return operation to get the DSO mapping name. By the way, you don't need to configure DSO return filter to get the updated values back from master destination record to source record. System automatically takes care of updating the values back to source when you modify destination master record. No need to write an explicit filter for this. You only need to make sure you have the mapping existing on the destination server which DSO can use to do the DSO update. DSO return operation can be used to return the ownership back to the source record. Hope this helps On Fri, Apr 12, 2013 at 10:39 AM, Nathan Brandt nathanrbra...@gmail.comwrote: ** Was trying out Return Operation with DSO. I have a Server A and Server B. Server A is sort of Source. I did DSO Mapping and was able to move data from A-Form1 to B-Form1 in Data + Ownership Mode. When TRANSFER is done, as expected, for the record in question, Server B is has Master Flag set to YES. Now If I delete this record from Server B, it automatically gets deleted From Server A. So far so good. But If I modify the record on Server B, changes are not coming back to Server A, so I guess Return operation is not working correctly. Interestingly Filter which I have written for B-Form1, does not ask for DSO Mapping moment you choose Action-DSO-Type (Return). I am wondering how Server B figures out what mapping is to be used for Return Operation and how to make Return operation work? Enabling Filter Logs on Server B shows this error USER: Distributed Server Overlay-Group: 1 Note: Distributed Server cannot transfer or return unless overridden Log file for DSO reveals nothing. ~ Nathan _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
DSO Return Filter
Was trying out Return Operation with DSO. I have a Server A and Server B. Server A is sort of Source. I did DSO Mapping and was able to move data from A-Form1 to B-Form1 in Data + Ownership Mode. When TRANSFER is done, as expected, for the record in question, Server B is has Master Flag set to YES. Now If I delete this record from Server B, it automatically gets deleted From Server A. So far so good. But If I modify the record on Server B, changes are not coming back to Server A, so I guess Return operation is not working correctly. Interestingly Filter which I have written for B-Form1, does not ask for DSO Mapping moment you choose Action-DSO-Type (Return). I am wondering how Server B figures out what mapping is to be used for Return Operation and how to make Return operation work? Enabling Filter Logs on Server B shows this error USER: Distributed Server Overlay-Group: 1 Note: Distributed Server cannot transfer or return unless overridden Log file for DSO reveals nothing. ~ Nathan ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
