Unanswered

PowerApps Grid Control not publishing to table

(0) Share

Report

Posted on by Bluey

Hi All,

I have been successfully using the Power Apps Grid control in a model driven app for several weeks now without issue. Yesterday the data stopped publishing back to the dataverse table. I have checked if other tables that also have this control enabled are affected and they are not. I have also disabled and re-enabled this control to see if this fixed the error, which it didn't. My conclusion is that the issue is with the table, but nothing has changed. Yesterday I did create roughly 2000 rows of data, and then delete them, could the deletion of the data be pending somehow, and therefore blocking any writeback function? I'm stumped.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (0)

Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@Bluey I'm wondering whether there is any logic that is preventing the records from being committed to the Dataverse table. Perhaps an error is occurring which is causing this. I would recommend trying to run the developer console in the browser's toolbar and review whether any console errors are shown in the log.

Was this reply helpful? Yes No
Bluey 30 on at

Like (0)

Report

This is the console error I am getting. This is past my understanding, but it is clearly not publishing back for some reason. Any Thoughts?

Was this reply helpful? Yes No
zuleika_v 15 on at

Like (1)

Report

Hey @Bluey

We are having the same issue. It's really frustrating. At a guess, there might have been an update pushed out for the power apps grid control that's caused this issue. As a work around, if you use the editable grid control instead, that seems to be working fine. I did have to set it up in the classic form editor though as it wouldn't let me save it without adding a child table from the maker portal. Not sure what's going on there.

I hope this helps in the mean time until there's some way to fix this.

Was this reply helpful? Yes No
Parvez Ghumra 1,579 Moderator on at

Like (0)

Report

@Bluey This may possibly be a bug in the Power Apps Grid control as @zuleika_v suggested.

Just to rule out any sever side issues, could you try creating/updating records in the target table without using this control, perhaps just manually as a test via a main/quick create form. Also try an alternative control (eg. the editable grid control, or an alternative grid control from the PCF Gallery.

If these options all succeed, then it's either down to a mis-configuration in your Power Apps Grid control (either as a result of a change being released by Microsoft, or a typo/bug in your configuration), or a Microsoft change has caused the bug (without requiring a change in your configuration of the control). Either way, I would suggest a raising a support request with Microsoft.

Was this reply helpful? Yes No
Bluey 30 on at

Like (1)

Report

@parvezghumra i have managed to fix the issue, but it still unsolved as to why it happened. I think you may be right about an update being pushed. Deleting the view and adding the columns back in one by one seemed to fix it. Oddly when I added all 50 columns from my original view all at once the same issue persisted. So I added one at a time thinking that a single column may have been causing the issue. One thing I did think may have caused the issue, is that a few days ago, I deleted a column because it had the wrong column type, and then recreated it with the correct type. The schema would be the same because the column name was the same. Could this have caused some sort type mismatch? This makes me uneasy because I’m concerned it will happen again. I’m keen to hear from the community if the issue gets solved.

Was this reply helpful? Yes No
rafaelsleao 11 on at

Like (0)

Report

the problem for me only appears when changing the value of a choice column.
it dont update unless I double click at it after changing the value.
then I can see the green check on the left showing it saved.

Was this reply helpful? Yes No