https://www.infopathdev.com:443/forums/44.aspx enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/82761.aspxTue, 18 Sep 2012 09:16:18 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:82761Jimmy0https://www.infopathdev.com:443/forums/thread/82761.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=44&PostID=82761400 rows sounds like a fairly big number.  I think the most effective solution would be to find a way to query fewer rows, either by filtering the query, or using cascading dropdowns.https://www.infopathdev.com:443/forums/thread/82743.aspxMon, 17 Sep 2012 19:03:07 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:82743InfoPathguy0https://www.infopathdev.com:443/forums/thread/82743.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=44&PostID=82743I have a form that uses the CRM 2011 rest service with a central dataconnection to retrieve a few fields and to populate a dropdown. This works fine when we have less than 400 rows. More rows, then it is not fast enough to retrieve and navigate while the data retrieved is stored in the session. My question is, is there some way to get better performance/workaround? Moreover, will I face the same issue if I have all the data in a SP list?