Ryan Cornfoot

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • in reply to: Multiple related fields #8768
    Ryan Cornfoot
    Participant

    Hi Alex,

    This solution works best for me, the load times are minimal and even though I am still getting “500” errors, it works for over 5000 items.

    Thanks Again.

    in reply to: Cascading Drop Down when more than 5000 items? #8766
    Ryan Cornfoot
    Participant

    I wasn’t sure Autocomplete could do it, but I have just seen your reply in the Autocomplete Forum.

    Ill have a go with that and see how it goes.

    Thanks for all your help Alex.

    in reply to: Cascading Drop Down when more than 5000 items? #8762
    Ryan Cornfoot
    Participant

    Hi Alex,

    It works, but the load time in IE8 is horrendous (Not your fault obviously)

    Google Chrome – NewForm Load Time = 7 sec (Up by around 5 seconds)
    Internet Explorer 8 – NewForm Load Time = 1 min 38 sec! (up by over a minute)

    Im going to try and go down the route of getting the threshold removed.

    in reply to: Cascading Drop Down when more than 5000 items? #8731
    Ryan Cornfoot
    Participant

    OK Alex, thanks for you time and efforts on this!

    in reply to: Cascading Drop Down when more than 5000 items? #8727
    Ryan Cornfoot
    Participant

    I have just tested the above theory, it does not work.

    Making it one field doesnt help either 🙁

    in reply to: Cascading Drop Down when more than 5000 items? #8725
    Ryan Cornfoot
    Participant

    I can try the one field yes, however I’m thinking I might try it a different way…

    User selects their Division, Business Unit and account, then enters their ID number this will pre filter the results to a maximum of 951 possible items. (Max people in any one account)

    Does that sound like it could make a difference? The reason I think it will is because the initial load query will only return 5 unique values (Divisions) Or do CAML Queries not work this way?

    in reply to: Cascading Drop Down when more than 5000 items? #8721
    Ryan Cornfoot
    Participant

    Indexing doesnt help 🙁

    in reply to: Cascading Drop Down when more than 5000 items? #8719
    Ryan Cornfoot
    Participant

    They are all basic data, name, divisions, accounts etc. Nothing Fancy, no metadata.

    Ill try an index now.

    P.S I have just checked the error in F12 Developer mode and it is saying the following: “The attempted operation is prohibited because it exceeds the list view threshold enforced by the administrator.”

    in reply to: Cascading Drop Down when more than 5000 items? #8714
    Ryan Cornfoot
    Participant

    Alex, Could this be related to the 5000 item threshold set by our SP Farm admin?

    in reply to: Cascading Drop Down when more than 5000 items? #8701
    Ryan Cornfoot
    Participant

    Dont know if this helps, its just a screenshot of the config, there are more Field Internal names but you cant see them due to length.

    Attachments:
    in reply to: Cascading Drop Down when more than 5000 items? #8686
    Ryan Cornfoot
    Participant

    It says something about field types but it works fine <5000 items…

    <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.</faultstring><detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">One or more field types are not installed properly. Go to the list settings page to delete these fields.</errorstring><errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x81020014</errorcode></detail></soap:Fault></soap:Body></soap:Envelope>
    in reply to: Cascading Drop Down when more than 5000 items? #8680
    Ryan Cornfoot
    Participant

    *Request Headers*

    Accept:application/xml, text/xml, */*; q=0.01
    Accept-Encoding:gzip, deflate
    Accept-Language:en-GB,en-US;q=0.8,en;q=0.6
    Connection:keep-alive
    Content-Length:1080
    Content-Type:text/xml; charset=UTF-8
    Cookie:_ga=GA1.2.140540675.1424861500; Ribbon.ListForm.Edit=632492|-1|328|-800423560; WSS_KeepSessionAuthenticated={9e742d76-c8cb-4594-a749-f80bafb31eca}
    Host:ameyportal.ameygroup.int
    Origin:http://MYSERVER
    Referer:http://MYSERVER/sites/travel/Lists/Travel%20Requests/NewForm.aspx?RootFolder=&IsDlg=1
    User-Agent:Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
    X-Requested-With:XMLHttpRequest

    *Response Headers*

    Cache-Control:private
    Content-Length:711
    Content-Type:text/xml; charset=utf-8
    Date:Fri, 09 Oct 2015 13:11:46 GMT
    MicrosoftSharePointTeamServices:14.0.0.6115
    Server:Microsoft-IIS/7.5
    X-AspNet-Version:2.0.50727
    X-MS-InvokeApp:1; RequireReadOnly
    X-Powered-By:ASP.NET

    *SPJS Version*
    1.252

    in reply to: Cascading Drop Down when more than 5000 items? #8661
    Ryan Cornfoot
    Participant

    I also get this error when Querying a list of 20K items, if I reduce its size it works fine.

    in reply to: Multiple related fields #8660
    Ryan Cornfoot
    Participant

    Or I may just use a lookup/cascading dropdown solution…

    in reply to: DFFS Rules Causing Major Slowdown SP2010 – IE8 #8649
    Ryan Cornfoot
    Participant

    Behaves perfectly using a lookup field, ill look into your autocomplete solution 🙂

    Thanks for looking into this.

Viewing 15 posts - 1 through 15 (of 24 total)