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...

Comments

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

Sitecore Stream - Platform DxP Evolution

Hi Team, I am absolutely Sitecore Stream enthusiast, and if you also keep following what is new in it and explore it features, This blog post is for you Since it was announced in symposium 2024 and probably the first platform DxP version package was released in FEB-2025 and we are now in Sep end and there have been significant roll outs and we are into 6th release of the platform DxP package. The purpose of this blog post is to summarize all improvements which came along with different releases for all of you and community, If you have not explored all of the packages. NOTE : Remember Stream is "AI capabilities throughout the composable stack, be it Content Hub, XMC, CDP, Personalized but this blog post is only for platform DxP package for on-prem XP/XM. If you see the image above, i have tried to show the package rollout on the timeline as an when they were released and watchout for next package rollout, For other useful features :)  Important improvements 1) Less configurations ...

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!!!