Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi,
I have created an address selector in Power BI by using a standard slicer with search enabled. However, the performance is very slow, just by using the slicer itself (i.e., I have not added any other tables or visuals to my model).
I import my table from Databricks, and it has ~2 million addresses. The slicer searches for approximately 5 seconds before it shows the resulting address. But if I use the address selector at, for example, this website (https://tjekditnet.dk/) it will search through ~4 million addresses in Denmark and instantly show the result.
Is the Power BI slicer search just inherently poorly optimized? Is there anything I can do to optimize it or an alternative option for creating an address selector? At a minimum, I would like to reduce the delay to 1 second.
Solved! Go to Solution.
@InlandEmpireMan , There is a new search text slicer, try that out
One thing which you can do is to change interaction so that it filter only other slicer. and then you use filter values of that slicer
Power BI Text Slicer Visual (Preview) Explained! Search by Text: https://youtu.be/3_j19r8XbI4
How to Use Multiple Values in Text Slicer- https://www.youtube.com/playlist?list=PLPaNVDMhUXGYo50Ajmr4SgSV9HIQLxc8L
Hi, @InlandEmpireMan
It sounds like you're experiencing performance issues with your Power BI report.This is a common issue when dealing with large datasets and complex calculations. If the data is very large, it's not feasible to import all of it. DirectQuery requires no large transfer of data, because it queries data in place.
You may consider using DirectQuery Mode instead of Import mode. This can help with performance by pushing the computation to the database server.
Connect Power BI to Azure Databricks - Azure Databricks | Microsoft Learn
DirectQuery in Power BI - Power BI | Microsoft Learn
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @InlandEmpireMan
It sounds like you're experiencing performance issues with your Power BI report.This is a common issue when dealing with large datasets and complex calculations. If the data is very large, it's not feasible to import all of it. DirectQuery requires no large transfer of data, because it queries data in place.
You may consider using DirectQuery Mode instead of Import mode. This can help with performance by pushing the computation to the database server.
Connect Power BI to Azure Databricks - Azure Databricks | Microsoft Learn
DirectQuery in Power BI - Power BI | Microsoft Learn
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@InlandEmpireMan , There is a new search text slicer, try that out
One thing which you can do is to change interaction so that it filter only other slicer. and then you use filter values of that slicer
Power BI Text Slicer Visual (Preview) Explained! Search by Text: https://youtu.be/3_j19r8XbI4
How to Use Multiple Values in Text Slicer- https://www.youtube.com/playlist?list=PLPaNVDMhUXGYo50Ajmr4SgSV9HIQLxc8L
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 54 | |
| 47 | |
| 39 | |
| 16 | |
| 15 |
| User | Count |
|---|---|
| 82 | |
| 69 | |
| 39 | |
| 29 | |
| 27 |