Forum Discussion
Using (2) parameters in a KQL function from Power Query
Ok, about to check myself into a ward.
Anyone had success with this? I've already developed a function in Kusto that takes the two variables; one string, one date.
The parameters come from a user.
Calling it from PQ is funky, imo. Funky in that it seems impossible.
let pinteresting = interesting,
peventdate = "datetime([eventdate])",
stringqry= "EventsParsed_FN([pinteresting],[peventdate])"
Source = AzureDataExplorer.Contents("https://<my>.westus2.kusto.windows.net", "<myDB>", stringqry, [MaxRows=null, MaxSize=null, NoTruncate=null, AdditionalSetStatements=null])
in
Source
😣
5 Replies
Please tell me this is possible.
What is interesting referencing? Is that some other query you have written? Is that supposed to be text?
What is "datetime([eventdate])" referencing. That is just text. What does the final outneed need to look like for stringqry and some example parameters? Is it upposed to to be text and date as a number?
let pinteresting = "interesting", peventdate = #date(2023,1,1), // or #datetime(yyyy,m,d,h,m,s) or #Date.FromText("1/1/2023") stringqry= "EventsParsed_FN(" & pinteresting & "," & Number.From(peventdate) & ")", Source = AzureDataExplorer.Contents("https://<my>.westus2.kusto.windows.net", "<myDB>", stringqry, [MaxRows=null, MaxSize=null, NoTruncate=null, AdditionalSetStatements=null]) in Source'Interesting' references a string variable that needs to come from the user. I have a Power Automate flow that will request the user input but have no examples on how to use it in Power Bi.
'eventdate' is also from user.
'Interesting' references a string variable that needs to come from the user. I have a Power Automate flow that will request the user input but have no examples on how to use it in Power Bi.
'eventdate' is also from user.
I developed a solution that takes SharePoint form inputs as variables which are then used in the query and are part of a flow. Works well, plus has the documentation of the request built in. It auto-emails the results of the query to the requestor and updates the SharePoint entry. The main advantage is the entire tool is packaged as self-service and the users love it.
