Power Apps grid control feedback

[jasongre]

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! 

[DKassian]

We're also experiencing this issue. Our current workaround is to go into the classic editor and add it there.

There has been a major regression in functionality over the past month with this grid component.

[Stevieed]

Yes I have to go to the classic maker portal to add it as well, confirmed.

The child item nested sub-subgrid is very useful and an important feature that the classic editable grid is very good at, and this new power apps control is just so **bleep**

[DKassian]

I am not sure what is going on on the microsoft side, but we found it got to a pretty stable place a few months ago, and then it's been seemingly getting worse ever since, which is upsetting (but not surprising with power apps....). This control is GA now so we have production scenarios that now use it. Frustrating to say the least.

Out latest issue also is that it's no longer possible to use the editable grid to change boolean fields, which is a frustrating change as one of out uses of the grid is marking child tasks complete via t/f field.

[Stevieed]

Yes we have experienced this issue a well, editable feature on some lookup field just randomly stop working, for example i found that if a grid has a AAD User lookup cell, it will 100% not allowing you to edit it as a editable cell, you have to go into that form of the record to edit that lookup field, very annoying!

[gsingleton]

@jasongre Hi, this control and its features are really important to a lot of orgs and people on here.  Can you give us an update and help us understand what is going on with it exactly?  People are seeing regressions in behavior and things generally are no longer working the way they once did.  A little bit of communication would go a long way.  Thanks for understanding.

[Schera]

Hi,

We have the Editable Power App Grid as a sub-grid on a form.

When the form loads and the user clicks (single) on a numeric column in the grid, the cell is activated. If he enters let's say "12" and presses tab/enter, only "1" will be stored in the field.

I am not sure if timing is an issue, but anyway tis is  a howstopper for production use in our case.

Hope this get's fixed soon.
Gerhard

[SimoneZink]

Just discovered today: Problem with editable fields in nested Records seems to be fixed 😀. I refer to this formerly problem:
"Although the edit option is disabled, certain field types can be edited in the nested record and the changes saved. In our case, this is critical because also read-only fields can thus be changed bypassing business logic and resulting in inconsistent data." 

We had the problem with option fields, but now they are properly locked.

[SimoneZink]

Also fixed 😀: If not all nested record can be displayed at once below the parent record, the user misses a scrolling-function to move up and down to navigate to the currently not displayed records.

User can now scroll through child records.

[Stevieed]

Extremely frustrating and annoying behavior!

When i copy and paste a column of grid from excel to this power apps grid control, it do allows you to paste into multiple cells, and protending to successfully saved values.

But you never get the saving progress bar next to the row when you normally see, the values will just appear there and does not save.

When you refresh the subgrid, the values are still there, but when you refresh the page or refresh the higher level form, those values will be gone because they never get saved! see video from youtube: https://youtu.be/IqNkDShurqI

[pioterpavel]

Issue The Associated Grid Control in Power Apps does not support custom buttons.

Impact This prevents users from adding custom buttons to the Associated Grid Control to perform actions on the data in the grid, such as creating, updating, or deleting records.

Workarounds There are a few workarounds that users can use to add custom buttons to the Associated Grid Control, such as using the Command Bar control instead of the Associated Grid Control, or creating a custom control that extends the Associated Grid Control. However, these workarounds are not as ideal as simply being able to add custom buttons to the Associated Grid Control itself.

Request Please add support for custom buttons to the Associated Grid Control in Power Apps. This would make it much easier for users to perform actions on the data in the grid, and would make the Associated Grid Control a more powerful and versatile control.