Re: Query for single item, rather than storing entire table in InfoPath

Jimmy — Tue, 18 Dec 2012 05:38:26 GMT

We typically do not recommend using DB connections for the main data source, as this imposes limitations on the layout of the main data source and limits the form in other ways as well.

What we recommend is to query the database through a webservice using a secondary data source. We have developed a generic webservice (QueryDB, part of DBXL) that people have found quite useful. Other options would include using a secondary data connection to SQL Server and using either code or qRules to modify the SQL query and query the database. The latter options require a bit more caution, as you need to guard against SQL injection.

Query for single item, rather than storing entire table in InfoPath

gilwoodring — Tue, 13 Nov 2012 19:51:14 GMT

I am currently connecting to a SQL Server successfully with InfoPath 2010, but I'm connecting to a table that has over 90,000 entries. In my InfoPath form I only require 1 line item (5 values from the line item to be exact, 1x5) to be returned, but have discovered that InfoPath wants to store all 90,000+ items in memory (90,000x5) THEN select the 1 line I need. Once this 1 line is selected, and the 5 values extracted, InfoPath STILL keeps the data intact when I save the file. Talk about overkill.

Does anyone know of a way to query for a single line item similar to how it is done in SQL? IE Select item1, item2, item3 from table ABC where this=that. I prefer a codeless option.

My goal is to simplify how users enter their data: Enter a part number, have InfoPath find the description, cost, and a few other values for ONLY that part number. All this needs to be a browser based form as well, running in SP2010.

Gil

Data Connections

Re: Query for single item, rather than storing entire table in InfoPath

Query for single item, rather than storing entire table in InfoPath