[elie]

Is there a way to mimic Netsuite’s dropdown fields (aka once the maximum number of items in the select are reached and it pops up in a new window instead) in a Suitelet?

We have a large listing of items that we’re drawing to a Suitelet form, but since it is numerous, it takes a very long time to search… we’d like to delay the search until 3 characters are typed into the select field, similar to the way NS handles items on a transaction line, or other fields… Is there a way to accomplish this?
This is a cached copy. Click here to see the original post.

[AE Cloud Consultants]

Hello Elie,

So in NetSuite you can go under Home – > Set Preferences, change the “MAXIMUM ENTRIES IN DROPDOWNS” to a smaller number. This should do the trick for you.

I am not sure if that will work for Suitelet, but if it wont, you will have to create two custom fields to chance this. One is a text field, and the other one is a drop down field, that is populated based on the text of the first field. When the user populate the text field, you will have to fire off a field change client side script that will limit the selection on the drop down list.

[elie]

Thanks. So, I am not fully understanding the suggestion, but the preference does not do the trick on custom fields on a Suitelet. I have dropdowns with literally thousands of options within; and the maximum for that preference is supposedly 500. I’ve played with this and this does not work, no.

In regards to the two fields, I’m not trying to filter out a field based on the text in another field; I want to mimic the behavior of native NS. . . Any idea?

[david.smith]

I’ve use the jQuery UI auto complete before when I was facing a similar situation.

http://jqueryui.com/autocomplete/

Basically what I did was posted the user input back to the suitelet to filter the search data. It was surprisingly fast and worked well. But it also meant that I couldn’t use a drop list. Of course this was also a custom input field and not a NetSuite field.

[elie]

Thanks, David. I figured we could do something like that, but that would mean pulling in the ID and storing in a hidden field, while showing the text in the displayed input field.

I’m just wondering, why is it not built in just like any native dropdown according to the preference set on my user account?

---

david.smith replied on 06/23/2017, 10:26 AM: That’s a real good question. I’m guessing the issue is that if your using a NetSuite record then the field know what to search. But with custom select options NetSuite would have no way of knowing how to perform the search.

On the flipside, NetSuite could store the data locally because it already is anyway and just filter that way.

Like the song says: “you can’t always get what you want”

[Author]

Posts