Thanks Ben, This sorts out my problem Erick
On Tue, Apr 24, 2012 at 3:51 PM, Ben Wolfe <[email protected]> wrote: > You should allow org.openmrs.Form/FormField/Field. Those are the core > openmrs tables you want to sync. You should disallow > org.openmrs.module.formentry. That contains the large xsn files you want > to block. See the large note on the formentry page for a little bit more > background: https://wiki.openmrs.org/display/docs/FormEntry+Module > > Ben > > On Tue, Apr 24, 2012 at 1:28 AM, Erick Mugoma <[email protected]>wrote: > >> Hi Mark and Ben, >> When designing forms we first set up the form schema before designing the >> infopath forms. >> >> It is possible to sync the form schema without syncing the xsns? >> >> Is there some way in which the form schema is attached or linked to the >> infopath forms (xsns)? >> >> I would want to ensure that no infopath form (xsns) gets to the sync >> queue any time we introduce a new form but the form schema should be >> synchronized. For now we have blocked syncing of the following objects: >> Form, FormField and Field. This means no form objects are synced. >> >> What options do we have to ensure that form schema is synchronized and we >> can manually upload the xsns on the individual servers? >> >> Thanks >> >> Erick >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >> OpenMRS Implementers' mailing list > > > ------------------------------ > 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]
