If you want one specific record to not go to a child server you can delete that sync_server_record row. I can't remember if there is a way to do this in the interface.
If you want one class of object to not go to one of the child servers you can configure that. On the parent server, edit the "objects not to send" list to have that object class. OR, on the child server, edit the "objects to not receive" list to have the object class. The former is a better option because then you don't waste time/space/bandwidth compiling and sending the object to the child server only to have the child server deny it. If there is an error in the sync queue at one child server it won't hold up the other child servers from getting their updates. However, that child server will continue to get a backlog of objects that will need to be sync'd. It is a good practice to check the sync queues every morning to make sure everything has been processed. Ben On Wed, Mar 14, 2012 at 8:04 AM, Erick Mugoma <[email protected]>wrote: > Looking at history changes ui on parent server, > Is it possible to allow a record to sync on one child server and not on > the other children within the sync network? > > I've noticed that if you mark the record as not for sync on one server it > does not do the same to all the servers. > > So wot happens when one sync record is synced on one server and not able > to be sync on the other children? Looks like it blocks the sync queue so > how do we resolve this problem? > > Thanks > > Erick > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
