Forum Discussion
Solved
Dynamic M query parameter binding to a query table
I am connecting to ADX, using Kusto direct queries. My users want to see the data for a specific ID, over a resonable amount of time. They are either facing lack of data (if no data for that ID), or ...
Thank you for your reply DataInsights. It turns out I was doing everything that your suggested solution in the other thread was proposing. However, I could bind my first parameter, but not my second parameter (that binds to the first returned query). I kept wracking my brains thinking it has something to do with the way my parameters were set up, types, or anything... Until the most obvious of solutions hit me. My second parameter was "loaded" into the report so that I can display the value that is being used. [/facepalm]
It turns out parameters must be NOT loaded into the report in order to bind them.
See if this solution can be adapted to meet your requirements: