As suggested by @mbilodeau in the thread Todays update broke dashboards - I am trying to rewrite dashboards to use the BAQ widget instead of the provider model invalidated property.
One issue I am running into is the where clause on the provider model seems to support a syntax that the BAQ widget does not. In the provider model you can use ?? before your binding and if its null that condition will be dropped from the where clause. But it the BAQ widget doesn’t seem to accept that syntax.
Whats the right approach here? Make a copy of the BAQ with parameters instead? Make a nest of if statements in application studio?
We’ve gotten hit by the same bug and I’ve got dashboards to rebuild too. I don’t have a solution for you that I know works but I suspect your idea of BAQ parameters is the route to go. I hope there is one that’s better as we’ll need it too.
I think you would probably need the if or switch/case to various instances of the BAQ widget. I would probably create a function to handle the where input parameters as separate strings and build the where out internally, then output the dataset.
I was about to stupidly ask if there wasn’t some way to force the provider model to call the BAQ again – somehow in thinking about the problem too long I forgot thats exactly what invalidated does
