InfoPath Dev

I am populating a dropdown list box from a sharepoint list.  Ther are approx 900 entries in the list.  The fist column of the list is identified as "Class" and for discussion sake has 3 different values: A,B,C, so, again for discussion sake, 300 A's, 300B's, 300C's.  Everything working ok, except I can only see the 1st 75 or so entries in the list, in this case all A's.  I added a uniqueness filter that seems to work if I Put a B or C within the 1st 75 entries on the list, but am basically unable to read all of the entries on the list in my drop down.  Does anyone know if there is a limit to the number of items contained  in a drop cown list box?(not just displayed as the problem persists even with the uniqueness filter in place)

 Someone was having a similar issue and the solution mentioned was altering the number of items to be displayed inside the SharePoint list settings.

jrudolph:

Try this:

Open the library, click on your view drop down option and click on "modify this view"

You should now be to a "Edit View: library name" screen.

Scroll down to the "Item Limit" option and expand it.

You should see:

Number of items to display:     Display items in batches of the specified size. Limit the total number of items returned to the specified amount. Change the "Number of items to display" to what ever you want and click "OK" to close the screen. From what I understand this should now allow your dropdown list to display up to the number of items that you put in the text box.

Looks like that's got it.  No if I can get my filters to work on the dropdowns cascading from this one, I will be all set.  Really struggling with the syntax of the expressions.  Looked in help file, not much help.  Do you happen to know of a good reference online or something?

Thanks,

CMH

Note: You should use CAML query if you have that manny items on a list.

1st time to use infopath, not real savy (Obviously), what is CAML query, what is the advantage?  I am currently setting this form up with cascading dropdown boxes (4), and am almost done (had uniqueness filters working, had cascade working, strougling with getting them working at the same time.  currently using this expression in the filter for the 1st box (working as it is just a uniqueness filter):

 not(. = ../preceding-sibling::dfs:Pipe_Classes/@Pipe_Class)

In the second box I have tried this which does not work for uniqueness + cascade functionality:

not(. = ../preceding-sibling::dfs:Pipe_Classes[@Pipe_Class = current()/Pipe_Class]/@size)       

The cascading structure is as follows (all boxes being pulled from the same sharepoint list):

User selects Pipe Class (Drop down 1),

This limits the selection available of "Size" (Drop down 2),

Which limits the selections available in "Component Type" (Dropdown 3),

Which in turn limits the selections available in "Description" (Drop down 4)

I am sure if I can get the second box working, I will also be able to get the 3rd and 4th boxes working as well.  Can you see / point out problems with my BLOCKED EXPRESSION?

Take a look at the following link which gives you the basics.

http://www.zimmergren.net/archive/2008/05/05/how-to-easily-construct-your-caml-queries-with-spquery.aspx

By default the SharePoint Views only display 100 items. Once you hit 2000 it gets really slow. So always try to return what you need in the query