I needed to write a query to interrogate attachments and determine for which ones the file paths were broken in some way.
I thought a UBAQ might be employed and found a thread on here from a little while ago detailing how to implement just such a technique and so avoiding a load of head scratching on my behalf.
Basically a GetList post processing directive on the UBAQ manipulates dummy calculated columns. Thank you - works great!
Anyway, then comes the next stage; Can it be made into a BAQ report with āfiltersā on the computed columns.
This doesnt seem to work. I sort of expected this might happen. The report option I guess is being applied to the SQL query before the post processing directive alters the resulant dataset
Is your goal to use a report parameter (input on the Report form, not an actual SSRS report paramater),as an input to the uBAQ, to be used to calculate a new value for an updatable field in the uBAQ?
Like if you wanted to replace part of the path in the image stores. Where input1 is the old path and Input2 is the new path.
Heās running C# code in the BPM on the updateable part which is filling in information in the grid after the query runs.
@richardh, yeah, youāre going to have problems with that in the report. Those BPMās donāt usually run the same way when you are running a report. Iām not sure how to get around it though.
You donāt even need an updateable dashboard. A regular one will do fine. The BPMās on an updateable BAQ will still run. The updateable part of the dashboard lets you change things on the dashboard. Which he probably isnāt doing here.
Yes. it is a non-updating updateable BAQ! I am just using a post processing directive to re-write a column in the returned dataset. It is quite a neat techinique really.
I came up with one solution for the BAQ report option; I added a pre-defined āReportParamsā - Check01
These are exposed to the report definition. as the dbo.BAQReportParameter_xxxxxxxxxxxxxx table
Then i have modified the query for the dataset to filter on this value.
Itās a rather inefficient process in SQL terms - the BAQReportResult_xxxxxxxxxxxxxxxxx table could contain 1000s of rows which are then filtered in the report generation.