Grid Filter - Ability to filter on a field that is not in the data source of the grid.

[frankiez]

I have a use case where a client wants to see all pending estimates by week ending and division. This is very easy. I can use a summary SQL view or a detail view which is then grouped and summarized in the data source of the grid.
The challenge is to filter the data by another column that is not part of the grid. There is a field called [ClosePercentage] which indicates the likelihood that the estimate will be approved. The use case is to now show all estimates with a closing percentage of 50 to 100%
Since this column cannot be grouped, it is not visible or part of the available fields on the grid. In MS Access, I can do this easily by writing VBA to construct the where clause as needed.
The question is how to add search fields that do not exist in the data source and customize the where clause to respect these new search fields.



Here is the SQL query use case. Any ideas would be much appreciated. Perhaps embedding the grid on a UX and then simulating the search part with UX controls. Selwyn did a video for this but the search fields had to match with fields on the grid which is not helpful for my use case. me. https://www.viddler.com/v/defa36db#errorExplanation

The grid contains CloseWeekEnding, Division, EstCount, EstimatePrice, EstProfit and EstProfitPct

SELECT
CloseWeekEnding
,Division
, Count(DISTINCT EstimateRevNo) AS EstCount
, Sum(EstimatePrice) AS EstimatePrice
, Sum(EstProfit) AS EstProfit
, iif( sum(EstimatePrice) = 0 , 0, sum(EstProfit) / sum(EstimatePrice) ) AS EstProfitPct
FROM Estimate.viwEstimatePendingDetail
WHERE CloseWeekEnding >= '6/1/2021' AND ClosePercentage BETWEEN .5 AND 1
GROUP BY CloseWeekEnding, Division

[Al Buchholz]

Can you make the summary SQL include

WHERE ClosePercentage BETWEEN .5 AND 1 .and......,rest of the selection criteria?

[frankiez]

Yes, but the .5 and 1 need to be arguments. The client wants a choice to see "all" estimates or any range of closing percentages which can range from 10% to 100%.

[madtowng]

I would expect this can be accomplished completely within sql, and the way I see it, the only need for an argument would be to define the date range.
If you could provide some sanitized data, it would make verifying the answer much easier. Another thing to improve the response is sql "flavor".

[frankiez]

I was able to accomplish the goal by embedding a grid on a UX. I used the UX to replicate the look and feel of a grid search part. When I perform a search from the UX, I call an XBasic function to pass the filter arguments to session variables. I then execute {dialog.EmbeddedGrid_NWORDERSGRID}.showAll(); to refresh the grid. I modified the onSQLSelectQuery and onSQLCountQuery server-side to construct the where clause on columns that don't exist in the grid. It worked as expected. You have to use Live Preview since session variables don't work in Working Preview. I also learned that once you change the base SQL statement, you must handle everything including totals, pagination, etc. This does involve extra work but at least I can see this is now possible.

It would be optimal if I can just change the filter so I can leverage Alpha to do everything else that it does inherently like record count, base SQL statement, pagination, totals etc. I checked OnSearchPartFilterCompute which works if you turn search part. The problem is I can't hide that section. I also don't know how to fire the OnSearchPartFilterCompute event from the UX. The {dialog.EmbeddedGrid_NWORDERSGRID}.showAll() does not trigger the OnSearchPartFilterCompute event.

I will share my final solution using Northwind sample database.

UX with an embedded grid. City is passed to session variable which becomes available in server-side events for the grid.
nwuxgridsearch.jpg

[Pat Bremkamp]

Another idea would be to use the search button in the UX to create a temporary table in SQL, then base the grid on that.