Re: Can you send data back the other way with Qdabra?

ErnestoM — Mon, 05 Apr 2010 11:56:01 GMT

The issue is that the source data is stored in XML, not in the database. So your third party software is modifying a copy of the data; there's no way (that I know) for the third party software to edit the xml and resubmit it to the Qdabra web service. Throughout this process, DBXL is the "owner" of the XML, the XML is edited via InfoPath, and the XML data is used to map everywhere else (SharePoint and SQL).

One option (in theory, I haven't tried this) is to change your InfoPath form so that it queries the SQL table on load (to get the latest values), but this requires a lot of work. Even then, SharePoint won't be updated when the 3rd party software modifies SQL. That will only happen when the XML is resubmitted via InfoPath.

Can you send data back the other way with Qdabra?

infopathman — Fri, 02 Apr 2010 19:26:49 GMT

Using Qdabara, we submit the infopath form to the Qdabra webservice and have the data posted to SQL server and also the forms saved in the sharepoint form library. That works great.

Now, the problem we have is a 3rd party program is modifying the data in the database - this means the forms in the form library have stale data! Is there anyway to have these DB changes somehow auto update the forms in the form library?

Qdabra Database Accelerator

Re: Can you send data back the other way with Qdabra?

Can you send data back the other way with Qdabra?