You’re offline. This is a read only version of the page.
The new Power Apps grid control in model-driven apps is officially in public preview! This control can be used for both read-only and editable scenarios, supports infinite scrolling for a modern browsing experience, and allows pro-dev makers to customize the appearance of cells. A new blog post and documentation for this should be available soon!
As you try out and use this new grid control, we'd love to hear your feedback! What went well and what didn't? What additional features do you want or need from the grid? This community post will be used to consolidate feedback on the Power Apps grid control. Thanks in advance for your comments!
Anyone having issues with the grid control lately being very non-responsive? Often just spins, and applying filters is now a bit of a buggy experience. Using the column filters often gets jumbled and when you open the advanced filter pane you have a bunch of field=* filters applied, or previous filters remain applied even when the "Clear" is selected on the column filter.
Users across our org are seeing this, wondering if we're the only ones.
Edit and save issues seem to have been fixed in the last few days, but aggregation and grouping by still don't work in my model-driven app. Is anybody else experiencing the same problem ?
Grouping by seems to call up another view than the one I want to group by, and aggregation does'nt display any result.
All was working properly 3 weeks ago.
Thanks
I have this issue too, it’s because in my grid I didn’t show the primary column in the view, so power apps grid control decided to add a place holder navigation button at the right hand side. But the development team didn’t properly code it so when the grid control trying to update value to dataverse, in the update message they included this place holder button, which obviously dataverse doesn’t recognise, so it fail without warning. The solution for now is always make sure you have a primary column in your view
Our PowerApps grid control is suddenly not saving data to Dataverse. There is no error message as well. Looks like the save itself is not triggering. Any one facing this issue?
Using the control in Power Pages, it is not possible to apply code customizations to the control as described here:
This means that it is not possible to apply cellRenderer and cellEditor overrides - eg. it is not possible to use
@chrisp_ph , the grouping/aggregation cannot be persisted or saved to a view yet in this first iteration, but that's where we'd like to get to.
When aggregation is enabled, the user can choose which column to summarize, but the setting doesn't seem to be persistent. When the user leaves the app and goes back in, the columns need to be summarized again.
In another word, can we make aggregations settings persistent ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
Share
Report
All responses (
Answers (
17
