Field parameters are a new feature in Power BI as of the May version.
With field parameters you can give the consumer of a report a lot of flexibility about the content of the report, what fields are used in the visuals, what time granularity is used and what measures are displayed.
All this without writing any DAX or M code.
In the attached example you can see additional use of field parameters left for you to figure .
Getting the data into Power BI
Start by connecting to the Azure Data Explorer (Kusto) connector and using the help cluster.
The help cluster is open for anyone and you don’t need any special account to use it.
Don’t forget to scroll to the bottom of the dialog and check Direct Query
Once in navigation you want to select the table TraceLogs in the database SampleLogs
Select Transform Data and you are in the Power Query editor
The table contains a log of ingestion files into Kusto back in one day in 2014.
We need to filter rows that contain Ingestor_executer in the component column.
An important column to look at is the properties column which is a JSON contain detailed information about each ingested file: Size, Format , CPU, Duration and more.
We want to use these values in the report, so we need to extract them from the JSON.
The JSON structure is stored in a string column so we need to first cast it to a dynamic type and then extract the elements from it.
We can use an M function to insert a KQL snippet as part of the query
We start by inserting a new step
The new step is created in this way
Now you can edit the statement in the formula bar and eventually it will look like this: