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.
Adding the name field worked for me. However, I would really like not to include it in the view as it's just noise for our use case.
I also tried editing the layout of the view using FetchXML Builder where I tried to hide the column using the ishidden property. However, that stops the editable grid from working, so the name columns needs to be visible in the view.
Our name column was setup using string prefixed autonumber so it is unique. This may be why it worked for us but not for you. You could try adding the primary key (GUID) as a column to the end of the grid - no idea if that would work but could be worth a shot for a temporary workaround until MS fix the bug.
Adding the name field has not worked for us either. The Name field is the Title field, tried adding either one to test and neither one worked.
Microsoft has confirmed this is a bug. They gave us a 3–4 week timeframe to get a solution in place. Adding the name also didn't work for us. ( Our name column isn't unique.) I had to revert back to the old editable grid instead of using the power apps grid.
I'm not having much success.
My main column was already in the view.
I realize my problem happens only when changing the value of a choice column.
If you just change the option value it won't save.
You need to double click it after changing, otherwise won't save.
Some additional detail - when I added the name column, it was the primary name column. However my primary name columns are renamed to xxxx- ID and are also string-prefixed auto number fields. This means that the primary name column is also unique on my test cases. I wonder if in this context since the Microsoft update, the control needs to be able to find a unique value in the primary name column to update. They may have inadvertently set the control to lookup the primary name instead of unique identifier, and it may error out when no uniqueness is found. Just guessing.
We did not encounter this error... (yet).
I hope it's not a new one that will start appearing in all environments...
Yes, adding the primary field of the entity did solve the issue.
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}"
}
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?