Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I loaded data from Azure log analytics dataset in PowerBi. The data in the table is something like this:
table - Log Analytics
Host | Server_Principal | ApplicationName | Text |
Host A | user_1 | Mashup Engine | Select * from DIM.Section |
Host A | user_1 | Microsoft Office | Select top 10 * from DIM.Section |
Host B | user_3 | Python | Select top 30 * from DIM.AssetLocation |
Then loaded all table names from the database that log analytics monitors in to Objects table:
table - Objects
Schema,Object
DIM,Action
DIM,AssetLocation
DIM,AssetStatus
DIM,BaseCode
DIM,RequestType
Object column turned in to slicer (with single selection).
What I am trying to do is to use slicer to find, show and calculate all records in Log Analytics table where selected table (for instance AssetLocation). Calculation works fine:
I can also find records and display by adding calculated column and then adding it to the visual (IsFound is True)
Thank you, @YukiK
I solved it by adding the crossjoin table on Objects[Object] and Log Analytics[Text] columns, then in Power Query used Text.Contains to generate a filter column, remove rows with where condition was not met and dropped the filter. Ended up with relatively small table that I added a couple of calculated columns and it did the trick.
In Power Query (or M) it works faster compared to DAX.
@pgolbiAwesome! Great to hear! Did my suggestion help (if so, please give it a thumbs up 🙂)?
Have you tried to add IsFound as a filter? That way, you won't have to include IsFound to the visual.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
18 | |
7 | |
6 | |
5 | |
5 |
User | Count |
---|---|
23 | |
10 | |
10 | |
9 | |
7 |