You’re offline. This is a read only version of the page.
4
I have built a model-driven Power App for a client. I am making extensive use of subgrids and the Power App Grid Control. Testers report that they are unable to use the column header filters on grids to filter numeric columns for values equal to 0, which is a legitimate value these columns can have. They reported it on a calculated currency column, but I have also seen it on rollup whole number columns and simple currency columns. The problem also applies to the other filter operators (less than, less than or equal to, etc.).
The screenshot is from a simple demonstration app I created in a non-client tenant, but it shows the same behavior the client is seeing. The filter does not consider 0 a legitimate value to filter on, even though it is a legitimate value for the column to have. This example is on a primary table grid, so it's happening even when I'm not using the Power Apps grid control on a subgrid. The record MP-1000 has a Model Price of $0.00.
This behavior does not happen when I edit the filters on the view; I can filter on values equal to 0 there. It's only on the column header filters on subgrids and primary table view grids. Update: On subgrids, it only happens when viewing the subgrid using the Editable Grid or Power Apps Grid components. When viewing it as a read-only subgrid, the column header filters accept zero as a value.
How can I get the column header filters to recognize 0 as a value on a numeric column? Thanks!
Share
Report
All responses (
Answers (
