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! 

[BenFreedman]

@jasongre Please bring back column left/right pinning! My clients were so excited about that feature and now it's gone.

[jasongre]

@DKassian Thanks for reporting these issues! We already had open bugs tracking the subgrid height issue and the Edit filters issue and are actively working to resolve these issues. We will look into the Open Record Set issue and get that fixed as well.

[jasongre]

@devlinl thanks for the question! Can you provide some more details about what you're looking for here, ideally with an example scenario? 

[jasongre]

@MichelH thanks for the feedback! Support for this grid in canvas apps is planned. Can you provide some additional details regarding your Excel comment?  

[jasongre]

Thanks for the feedback and suggestions, @MarcRu! Full support for offline mode is in progress. We will consider extending the grid's capabilities with items like creating records inline in the grid and more customization options after this grid reaches general availability.  

[jasongre]

Thanks for the feedback, @MattVizor ! Can you provide additional details regarding what you are looking for here, ideally with an example scenario? Is the capability you're looking for available in the legacy grids? 

[jasongre]

Thanks for that suggestion, @BenFreedman, and I agree with you! There are some accessibility challenges with that capability that need to be resolved before we can surface it in the control.  

[devlinl]

I want to be able to both view and edit Multi-Table Lookups.

I think the view scenario is pretty self-explanatory.

For the edit scenario, I want to make sure that, when a Multi-Table Lookup Column is included in the view, I am able to select records of any of the types targeted by the Multi-Table Lookup.

So, for example, if I have a Media column, which can point to a record in either the Books, Audio, or Video tables, I should be able to lookup and select a Book record, Audio record, or Video record when editing the Media column in this new grid.

[DKassian]

Another item that has been a concern to us across the platform with the fluent combobox controls in custom pages, and also with the editable grid is the lookup dropdowns only displaying the primary name field. This makes it difficult to find the correct information when one field isn't enough. On the current dataverse model driven lookup controls we have the ability to set the lookup to a view, with 2 fields shown in search, and more available with selecting the expand chevron. Other platforms such as D365 finance give a mini grid to select from when searching a lookup.

This is more of a general feedback item, but for example if selecting a contact record, only having the name field in the lookup isn't useful as there can be duplicates, etc. What you really need is the account + contact name to be able to select the correct one. In the scenarios where we have only one field shown we have to make 2 cascading lookups, the first for account, and then a second filtered lookup for contacts. While that structure works in some scenarios, it's not ideal and definitely more complex for users than the preferred alternative of being able to see multiple fields in a lookup dropdown searchbox.

To get around this in custom pages, we've resorted to developing a custom PCF, and possibly we could with the new grid with the component customizer, but our devs have not looked into that yet.

Something to consider as the platform further develops.

[MattVizor]

Thanks @jasongre 

Simple scenario:

We currently have a table with a 1:M relationship with another (completion of these secondary records is required to mark the former as closed).  In that second table, there is a lookup field which is filtered to related records. 

e.g.

Primary Record 1 with a  links to Secondary records 1, 2, 3, 4 (questions related to a specified type for Primary Record 1).  Within those Secondary records is a field 'answer' which filters based on a field in Secondary records

The aim is to stop users having to access individual records and step through each related using the 'Open Record Set' function as that then requires them to close multiple records as they close to get back to the original Primary Record

I look forward to your comments