Data Connections

Re: How many is too many?

CGann — Mon, 10 Oct 2011 17:58:34 GMT

I've paired it down to 2 data connections. One pulls a dozen or so items from one list but the other powers a filtered text box value (@Level[@Title = Account] -Get the value of the account level where the list title field equals the account selected in the dropdown.) I've put the 2048 account values on the form but the data connection still has to pull 2408 rows to get "Level".

I'm still getting the "Stop running this script? A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive." error.

It seems that every time a field on a view is changed, some script is called and this error pops up. I don't have validation or rules set up on any of these fields and I've also set them so that they don't send info back to the server. FilterOwssvr won't be of any help because there's nothing to filter on. Do I just tell the users to "live with it?"

Re: How many is too many?

CGann — Wed, 05 Oct 2011 13:08:18 GMT

Thanks Pat. I suspected as much. Definitely pulling back more than 100 rows. For one dropdown they're actually pulling back closer to 2500 items. Also, they're not using a DCL, just in-form data connections. I'm checking to see which dropdowns' source data doesn't change much and move that content directly to the form in lieu of data connections. More contraints are: no back-end code (C# or VB), has to be browser enabled, trying to avoid administrator involvement.

With that in mind, any other tips you can share?

Best!

Re: How many is too many?

Patrick Halstead — Wed, 05 Oct 2011 06:57:46 GMT

Hi CG,

Yes, you're right.

Sorry to hear that you are having to defuse a roadside bomb. Twenty data connetions on load is too many. The form is a "cluster cluck" as they say here in Chicago (in Seattle Speak: sounds like the form has some serious precipitation issues). Best practice is one data connection that pulls in all values or if the number of rows is >100, you should use a filtered data connection based on a parameter from a field in your form (search for FilterOwssvr or QuerySharePoint).

How many is too many?

CGann — Tue, 04 Oct 2011 17:59:41 GMT

I just inherited an InfoPath 2007 form. Currently, users are getting the pop-up error "Stop running this script? A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer might become unresponsive."

As I dig into the form I see the author had created 21 data connections. Upon closer inspection I see that each data connection is pulling a single data field from the same list.

My questions: Are all these data connections what's causing the long running script error? Would it be more efficient to use a single data connection that pulls all the required data fields?

Thanks in advance!