Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi All
I am working on a custom data connector for powerBI and am wondering if it is possible to override the behaviour in the list search box.
Some more details: I am needed to be able to search through this list of items in the navigation table for my custom data connector. Some of the time I can simply load in the ~500 items and leave the default search behaviour to do it's thing, this is not an option when in some cases there are more than 150,000 items to search through, as the server pages these items, my code currently loops through all those pages and puts them into the search box, which can take faaarrr too long in cases like this. What I am looking to do is to override the search box listener so whenever a new character is entered that is instead when it sends a request to my server and the server get's the first 50 result and responds with those etc etc.
Is this possible, or is there a better way?
Any help is greatly appreciated.
Hi @Anonymous ,
We can use the custom visual text filer and slicer to work on it.
Hi
Thank you for your response.
I have since looked into this and unless I am missing something this is not suitable for my needs for a couple of reasons. The main one being that I need this to happen in the navigation table stage of importing my data into power BI through my custom data connector.
What I am trying to do is this: The user opens up the data connector, signs in to their account, and then in the navigation table has a list of various datasources that they have access to. Each one of these datasources contains anywhere from 100 to 160,000 items and what I want to do is allow them to select which of those items they want, without having to load in all the items at once. This works fine if you know the names of the items and can just type them in but often the names are long and obscure, hence the need to search for them. However to search for them you either need to have loaded them all in at once, not an option due to time (and to a lesser extent memory) constraints, or have a way to query my API on every keypress of the search bar, leading me to wonder if there was anyway to override the search bar listener.
An alternate solution that I have been looking into if it is possible is to have a nested function inside the navigation table, so I could manually query the api from there and then use that response in the encompassing function to get the items I wanted.
Actually let me make this a little clearer as to what would be ideal
This is some of the code behind my navigation table.
I currently have all the tags being loaded by my GetAllTagsList function, and then displayed in the metadata Documentation.AllowedValues, what I ideally want to be able to do is get the current input into the search box as showed in my original post and pass it into a function which Documentation.AllowedValues uses.