Skip to main content

Telerik Mvc Combobox large data loading issue on AutoCompleteFilterMode

Hi all

Its been long break...Here i am back with little out of box solution which is not available on internet,i did the solution and felt to share it with you all so that you people do not face the issues which i faced while working with telerik mvc combobox

As we know (People who use telerik mvc combobox) that when telerik mvc combobox is used and there is huge data to be loaded from controls action method, and if AutoCompleteFilterMode is on,the combo simply hangs in IE and traditional IE error will come up saying "SCRIPT IS RUNNING INFINITE,DO YOU WANT TO STOP THE SCRIPT", and will just kill the browser

So, let us cut the story short and come up directly on solution,say you are having following combobox code

<%: Html.Telerik().ComboBoxFor(model => modelfooId)
.AutoFill(true)
.BindTo(new SelectList(Model.fooList, "Value", "Text", Model.fooId))
.HtmlAttributes(new {style = "width:400px"})
.Filterable(filtering => filtering.FilterMode(AutoCompleteFilterMode.StartsWith))
.ClientEvents(c => c.OnChange("MakeSelection").OnClose("MakeSelection"))
.HighlightFirstMatch(true)
%>

you can observe the client event registered,which is actual hack for the solution,now those javascript function is as simple as that like following

function MakeSelection(e) {
    $('.t-animation-container').hide();
}

Now, try refreshing your page and try selecting any of the options, it will not hang and will run as you want

Its like magic,"Its misty until you know the trick behind"...

let me know your feedback...
Labels:

Comments

Post a Comment

Popular posts from this blog

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...
2 comments
Read more