Update to a previous topic about Manual Entry Search Chips not working for BAQ Reports

I came across a helpful post while struggling with why I couldn’t key in a value in a BAQ Report filter (I had to go through the search process to add search chips).

For what it’s worth, we can populate the search chips using a text area (text box will probably work too). I created 3 text area fields and set their EpBinding to ReportParam.Filter1, ReportParam.Filter2, and ReportParam.Filter3 respectively. Entering “~” separated values into the text area fields populates the search chips.

Until they give the BAQ Report filter parameters the ability to validate keyed-in values, I think this might be a decent workaround. We’ll see!

1 Like

Hi,
Consider creating reports using RDD—it’s a fast and efficient approach. You can also bind your BAQ filters directly to the report filters