# Row-Level Actions Not Displayed on Landing Page when allow querying on any column unchecked **URL:** \ **Category:** User Experience\ **Tags:** user-experience, pega-platform\ **Created:** [July 30, 2026, 2:52pm UTC](https://forums.pega.com/t/row-level-actions-not-displayed-on-landing-page-when-allow-querying-on-any-column-unchecked/12940 "2026-07-30T14:52:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![SSrinivas](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/ssrinivas/32/22334_2.png) [@SSrinivas](https://forums.pega.com/u/SSrinivas)\ **Post date:** [July 30, 2026, 2:52pm UTC](https://forums.pega.com/t/row-level-actions-not-displayed-on-landing-page-when-allow-querying-on-any-column-unchecked/12940/1 "2026-07-30T14:52:26Z")
We have a **Category** case type and maintain multiple **Product** records under each Category. On a landing page, we display the list of Categories through a **Data Page** sourced from a **Report Definition**. The Report Definition includes an **association join** to the Product data and uses an **aggregate column** to display the **count of Products associated with each Category**. A **Post Data Transform** is used to flatten and format the results for display. As the source records are work objects (Category cases), we want to enable **local actions at row level** from the landing page. However, despite enabling all relevant configurations, the row-level actions are not displayed. During troubleshooting, we observed that enabling **“Allow querying on any column”** on the Data Page causes the row-level actions to appear and function correctly. However, once this option is enabled, the **aggregate count calculation in the Report Definition no longer works as expected** , because of runtime query. Declare expression also not working if we check allow querying. Also we cannot use **Insights** for this requirement, as it introduces additional capabilities and interactions that are not aligned with the business needs. @MarcCheong@RameshSangili ---
**Author:** ![MarcCheong](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marccheong/32/23266_2.png) [@MarcCheong](https://forums.pega.com/u/MarcCheong)\ **Post date:** [July 30, 2026, 8:34pm UTC](https://forums.pega.com/t/row-level-actions-not-displayed-on-landing-page-when-allow-querying-on-any-column-unchecked/12940/2 "2026-07-30T20:34:55Z")
I would expect that, Constellation functions tie into queryable data pages a lot. Could I understand a bit more on the UX you’re trying to achieve - you want to show a list of cases AND counts? I don’t understand how that works with our current table components. Unless you made your own, I have seen attempts to create totals under embedded or data reference tables (like Insights does) My gut would of been to go with Insights, but you have rule that out (more on that later). So if count’s are important, do they have to be inside the data page? 1. You could use grouping? That has a count natively 1. ![solution 2](https://pega1.discourse-cdn.com/pega/original/3X/f/5/f556c7f1e2b957bf90023f133b432e095564620c.png) 2. You could put the counts outside the table context? above or below with the relevant counts? _I would need to understand the use case and UX a bit more in depth to be sure this would actually solve the business need._ **Insights** Which insights features don’t align with business needs? '26 does introduce some more controls on what is shown and not. ---
**Author:** ![RameshSangili](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/rameshsangili/32/23377_2.png) [@RameshSangili](https://forums.pega.com/u/RameshSangili)\ **Post date:** [July 31, 2026, 10:22am UTC](https://forums.pega.com/t/row-level-actions-not-displayed-on-landing-page-when-allow-querying-on-any-column-unchecked/12940/3 "2026-07-31T10:22:48Z")
> [@SSrinivas](#): > > During troubleshooting, we observed that enabling **“Allow querying on any column”** on the Data Page causes the row-level actions to appear and function correctly. However, once this option is enabled, the **aggregate count calculation in the Report Definition no longer works as expected** , because of runtime query. I agree with @MarcCheong recommendation. Since the requirement is essentially to display Category records along with the count of associated Products, and the relationship can be achieved through an Association rule, Insights seems like a natural fit for handling the join and aggregate count using Group By as suggested.