Re: Bad Performance multiple cascading fields

Hilary Stoupa — Mon, 26 Sep 2011 20:08:29 GMT

Hi -

It seems like it may be hard for a user to select an option from a list with 5k items.

Any way to filter those down further?

As to the general responsiveness / performance issue - on your dropdowns, do you have the checkbox for only displaying unique items selected? I had a form with ridiculously bad performance once where that was the culprit.

Have you thought about only querying for the items you need if you are returning all items?

Bad Performance multiple cascading fields

AMeesters — Wed, 21 Sep 2011 12:35:52 GMT

Hello all,

This is my first post ever, so I hop my writing makes any sense.

I changed a standard list form with Infopath 2010 to crate a custom Action list. Among other fields, it contains 10 cascading dropdownfields (all linked together). The data for these fields are retrieved from a secondary dataconnection (a SharePointlist named Inventory). This list consist of the same fields as my form as lookupfields to other lists (like location, stationstype or systemtitle). To show readable names in my dropdowns instead of ID's, I have dataconnections to the other lists (location, stationtype, systemtitle) and use filter these with ID's stored in Inventory. Here's an example of the xpath filter I use to show the systemtitle (see also attached logical diagram):

Datasource: Systemtitle
Filter: ID = Formula:
xdXDocument:GetDOM("Inventory")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Systemtitle[
../d:Locationcode = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Locationcode and
../d:Stationtype = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Stationtype and
../d:Functie = xdXDocument:get-DOM()/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW/my:Function]

The functionality works...but is really slow. It takes about 13 seconds to get control of the next field. Because some of the list are really big (4950 items), I changed the moment of retrieving te data from start-up form to field change and back, that didn't make any difference. I indexed the collumns, that didn't help. I read Micorsoft's info about Infopath and performance, that didn't help, neigther the two days I spend on fora for this subject. It seems to be that filtering the data in the Inventory list and retrieving the names from a second list gives the problems. Maybe my xPath isn't tight enough or the XML structure (how can I change this last one when I use a SharePoint list?). There are other rules in the form, which are not triggered by the change field of cascading

Worst thing, it also slows down other parts/cascading dropdowns in the form. Does anyone have a solution to this problem without coding?

Thanx for your replies in advance.

Arthur

General

Re: Bad Performance multiple cascading fields

Bad Performance multiple cascading fields