Power Apps Grid Control on Subgrid - editable - doesn't actually save

[MJC]

I'm quite sure this worked a few weeks ago.  When you add a subgrid to a form, and then add the power apps grid control, and set it to enable edit in the main grid, it appears as though it worked.  However, when you enter information or change an option from yes to no, and then navigate away from the record, your changes are not saved.  The old editable grid works, however the new power apps grid control is not working in this context.  Does anyone else see similar behaviour?

There are no errors or warnings and it appears to save, but when you navigate back, the update is not saved.  The control seems to work fine on views, just not on forms with related data.

[JTJO]

I have a client that is experiencing the exact same issue. It seems to have just happened in the last 24 hours, all of a sudden the grid control is not saving any changes.

[fpm]

We are experiencing the same issue since last week. The save event is simply not triggered at all by the grid when clicking outisde of the row.

Microsoft recommended us adding in the grid view the primary column of the entity (which does not make much sense, as this was never a requirement for the editable grid). This did solve the issue for some users, but others are inexplicably having the same problem. 

We belive it was caused by an update pushed by Microsoft, that messed up the control. As always, they do not feel responsible for it....

[MJC]

That is a terrible response to this problem from Microsoft! I wonder if those users who still had the problem after moving the grid were using a cached version of the control?  We've had quite a few caching issues when we push out updates to users and usually have them try CTRL + F5 in the browser (this forces a page to pull latest pages from the server and bypasses the cache). 

I'll put in a support request to Microsoft also today and see if they have a different response.  I have noticed the grid control is updated almost every week so it does appear to be under quite active development.

[fmoscu · Accepted solution]

It appears is actually works if you add the 'Name' column.

This column is there by default in the classic editable grid whether it's in the view or not, but it is hidden and it's added by the grid in the background, not displayed as a column on the grid itself.

After a very recent update, I suspect the one from April 28th, it appeared this new requirement to include the 'Name' column in the view used by the power apps grid control. This means that the column will always be visible (and editable, unless you add code to disable it) whether you want it or not....

[MJC]

Just tried this and confirmed - nice find!  This is better than our current workaround.  I have also submitted a ticket to Microsoft, and referenced this thread in the case.  Thanks @fmoscu !

[MJC]

Marking solution for FMOSCU as it seems to be a Microsoft Bug, but this workaround is suitable for now for our use case.

[Jmorris0923]

We are having this same issue. We have changed back to the old editable grid as our workaround. We use this grid daily and have only started encountering this issue at 8AM today. Submitting a ticket to Microsoft. 

[KASCHN]

I am also encountering this in a client application where we use the power apps grid on a main grid menu item. I already have the "Name" field included in the view and it is not working. Am I understanding your workaround correctly to add "Name" field to this Active Item View?

[Jmorris0923]

Update -We are working with Microsoft. We were able to add the name column and we still had no success in getting this grid to save. I do have some tracing errors that you can check for in your Dev Tools.  No solution as of now, but we are working on it.

{
"0": "{\"errorCode\":2200000006,\"message\":\"Cannot save due to no dirty changes.\",\"blockErrorReporting\":true,\"faultedRequestIndex\":-1,\"errorSource\":0}"
}