Hello.
I have several BAQ’s (mostly used by Quick Searches or called searches) which have columns that I want to suppress from the resulting data grid.
For example, I frequently use Calculated fields because they allow me to do things like concatenate all the address fields, or maybe build a string of characters that are used elsewhere, but would look strange the average end-user. The concatenation method is great for doing a WHERE search against, but again looks strange to the end-user.
Is there any way to suppress columns from the grid which I need to use for internal purposes so our users don’t have to wade through what most certainly looks bizarre to them?
you can hide them in a DASHBOARD, but not in the query or quicksearch. One solution is to pass a PARAMETER to the BAQ, and have all the filtering done directly in the BAQ rather than sending all the BAQ Data to the quicksearch to apply a filter against.
1 Like
Thanks Tim. Your response looks like it belongs with my previous post about passing parameters from a QS to a BAQ, but then again, that proves the point that they are equally similar and can only be done via programming. In my conversations with some of the TSG developers, E11/Kinetic is replacing much of the free-form coding ability with “canned” functions. Perhaps at some point in the future, Epicor would allow us to pass something like [EpiBinding:OrderHed.OrderNum] as a constant:
Hi Tony,
May I suggest that in your BAQ, change the Top Level query (the one that displays the data) into a subquery.
Make a new Top Level query (in the BAQ) that gets its data from the subquery, and use this to display the data you want. Subqueries are added on the Phrase Build page and TL and Subqueries are changed at Subquery Options. ( subqueries are easy to use and provide a lot of power and flexibility).
