We have several grids to which we've added both standard and custom fields that have a fixed relationship to another table. Take, for example, the price group in the customer grid, which filters the price group table by the field “module” for those lines with the fixed value “customer”:
We can see that if we expand the field to select a value, it only lets us choose customer price groups. However, if we go to the grid filter and try to select a value to filter by, it loses the module-based relationship and shows us all possible values from the price group table, including those from inventory or vendor modules:
Is there a any configuration or simple programming task that would allow us to prevent this standard behavior? Some of the fields we want to filter have a large number of records, and this is not very useful for the end user. We have done some test with custom lookups, but they are not useful for grid filters.

Report
All responses (
Answers (