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! 

[jasongre]

Thanks for the feedback, @Anonymous ! Both are great suggestions! 

[Yuni_H]

Not sure if anyone else is having this issue - I'm using the Power apps grid control in a subgrid of an entity form. When I add records that is greater than the maximum that will show in the subgrid, it only show the last few records that didn't fit in the view. The view that lists all the records with scroll bar appears if I refresh. This also happens when I resize the browser, it goes back to the view that only shows the last few records.

This is how it looks with the issue:

This is without the issue:

When I scroll down to the bottom, see those records in the first screenshot:

[DiogoVieira]

I noticed that every time I expand a child dataset (highlighted area) it always appears an error in the console.

Error: 

And also, I added a JS event to the grid control, if I put the any event on the Main Record (Solution) it works, however if I put the same script on the child records (Line Item) it doesn't work, anyone experienced this as well?

[SimoneZink]

We have high hopes for the Power Grid control, as the (announced) features have great potential to solve immediate problems and requirements of our users. Currently, a robust nested records function would save us the development of a complete canvas app. 

Unfortunately, the function cannot yet be used in any our requirement cases for the following reasons. Can we expect further development regarding our issues this year?

1. This is a showstopper:
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 field changes in this way do not trigger plug-ins, for example, and business logic is subverted, resulting in inconsistent data. The editable field types I discovered so far are 2-option and option fields.

2. This leaves an unprofessional impression:

If not all nested record can be displayed, the user misses a scrolling-function to move up and down to navigate to the currently not displayed records.

3. This is cosmetic, but unused, empty space is always an annoying issue:
Users (and me 😉 today expect the interface to adapt to the content to see as much content as possible at a glance.

[LinnZawWin]

@jasongre 

Some more issues regarding the lookup field in the editable grid are reported in this thread too.

https://powerusers.microsoft.com/t5/Building-Power-Apps/Power-Apps-Grid-Control-and-using-the-Lookup...

• The lookup list only loads the first page and it is not infinite scrolling (unlike the normal lookup control on the form
• Anything that we choose in that Items > Lookup configuration is working (Default View, Record Filtering based on another column)

[SimoneZink]

Update: the Plugin ist triggered correctly, but delayed in our case so it only shows after serval refreshes. Still the issue that Option-Fields are editable ist a show stopper, as thus read-only field set by code can be changed on netsted level anytime manually and data consistency ist lost.

[DKassian]

Disappointing to see the vertical lines removed from the editable version of the grid! That was helpful to our users in testing to identify when a grid was editable, and most preferred it all around as it's more clear the separation between data elements.

[Stevieed]

1, child record nest grid is very unstable, sometimes it works, sometimes it doesnt, this is very annoying

2, lookup field doen't want to be filtered as what i set in the settings

3, child records will not have all items display wtf

4, read only field is editable on the grid wtf

conclusion: this is still a garbage

[DKassian]

Also I have noticed these past few days the ability to extend the height of the subgrids on a form has been removed, similar to back early in the preview. I see a lot of seemingly previously resolved issues have come back, like the editable child record issue, etc.

It's like we've been reverted back to an old version of the grid. 

[Stevieed]

Now it just doesnt even want to save the form if you add the power apps grid control on a form

whoever coded this must be fired from Microsoft, terrible product