Inconsistent Search Case Sensitivity Between List View and Lineage View

[MMSBMSRDP]

I’ve identified an inconsistency in the Power BI service where the search functionality behaves differently between List View and Lineage View. In List View, the search is case-insensitive (e.g., searching "report" or "REPORT" yields the same results), which aligns with expected behavior. However, in Lineage View, the search is case-sensitive (e.g., "Report" and "report" return different or no results), which feels unintended and disrupts workflow when navigating dependencies. This inconsistency can lead to confusion and reduced efficiency, especially for users relying on consistent search behavior across the platform.

[tayloramy]

Hi @MMSBMSRDP, 

Are you able to post screenshot of this behaviour? 

I'm not seeing that in my enviornment: 

If you're able to post some screenshots of the behaviour, we might be able to reproduce it and then report it to Microsoft. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution
 

[MMSBMSRDP]

List View Lower Case with resultsLineage View Lower Case no resultsLineage View Case Sensitive with results

[tayloramy · Accepted solution]

Hi @MMSBMSRDP, 

That's facinating, you are seeing compeltly different behaviour than I am. 

What are your permissions on the workspace? That shouldn't matter but maybe it does? 

I also see that your workspace is not attached to a premium or fabric capacity, so perhaps there's a difference in behaviour in premium vs non premium workspaces? 

This seems like a bug. 

Do you by chance have a premium workspace you could use to test this theory? I will also test it from my end and see what I can discover. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.