nbuytaert1
commented
9 years ago Would be a great enhancement indeed. I can't add new component attributes anymore since I have reached the limit of fifteen attributes. Pretty stupid, but I can't change that.
Another solution would be to allow an extra column to be used in the item's LOV definition. That way I can easily differentiate between the display column and the search column. I'm not completely sure whether this is a valid option, so I should test this out.
I'll take a look at it when I find the time.
Right now, when you enter a value in the search field, you'll search the displayed column. Maybe it's a good idea to add a new attribute at component level, where you can add an alternative search filter? That way, I could also search on a column that's not displayed such as a customer number, or use an Oracle Text contains index to speed up a like lower('%x%') query (and that way, you can search multiple columns easy and fast).