Values for a column not shown in Views - Model-driven App

[MattB_Motive]

A user had created a number of views and shared these across the organisation.

One particular field, a Whole Number data type (formatted as a duration), showed up as blank. When the user opened a specific record, the duration field would then show up for that record and any other records that had been opened. When the user disconnected from the internet and reconnected, the column was empty again. This effected other users across different browsers, devices and OS (Mac and Windows).

The duration field is a simple type (not calculated or rollup) but is populated by a simple Javascript web resource from a start date/time and end date/time field.

We looked at the FetchXML of the affected views and the duration field was missing. We asked the user to remove and add the duration column again, and all values showed up in the view (and in the FetchXML). This appeared to resolve the issue for everyone.

Approximately a week later, the duration column was empty again. However, this time the FetchXML looks OK as do the network logs. Again, this is happening to different users, across different devices and browsers - it is also happening across different environments (dev/test/prod). When adding the duration field to an existing view it also shows up as blank. If you export the view to Excel, the values are displayed.

A browser refresh looks to have resolved the issue for each user. 

Does anyone have any clues as to what may have caused this? And how to resolve it for good?

[NeerajGargi]

This sounds like a browser caching issue. Try to hard refresh ctrl+F5.

[MattB_Motive]

Thanks, as I mentioned a browser refresh seems to have resolved the issue, at least for now.

I was hoping to get a better understanding of why this is happening. Especially since it is affecting different users across different browsers, devices and OS. Does it make sense that it's a browser issue if it's happening so broadly?

[NeerajGargi]

I think i know where is the problem. As you mentioned that field is being populated through JavaScript expression, this means, by default field is empty when user views the record in a View. But when user opens the record in a form, field gets populated through JS expression. This makes field get a value next time when user view record in a View.

In my opinion, instead using JavaScript to populate value into the field, you should use backend workflow or Power Automate flow.

[MattB_Motive]

Good suggestion. We initially thought it may have been a JS issue (or something to do with the column configuration) until we found the issue with the mismatched FetchXML and LayoutXML - which was resolved when the user removed and readded the duration column in the view.

The values do exist in the records - they are visible in both the Excel export as well as the backend Table view. You can't create a record without the duration being populated. They also appear once the user refreshes the app.

There was a business requirement to have the duration calculated and visible to users when creating a record, hence the use of JS. 

[MattB_Motive]

After a lot of testing we were able to narrow down the issue. It appears that the duration column is intermittently showing blank values when using the 'Power Apps Grid Control' (including the default view of the new modern look).

The values are displayed properly when switching to the 'Read Only Grid' or the 'Power Apps Read-Only Grid'.

Alternatively, refreshing the browser will make the values display properly in the 'Power Apps Grid Control' but this is only temporary and the issue will appear again in a few days. Since the duration column values are displaying properly with two of the controls, it seems like the issue is with the Power Apps Grid Control rather than with the duration column or views.

We were also able to recreate the issue in a separate developer tenant - once again the values displayed correctly when using the 'Read Only Grid'/'Power Apps Read-Only Grid' but were blank with the 'Power Apps Grid Control'.

@jasongre - we have created a support ticket for this issue (Support Request ID: 2402030030000238). Are you able to assist?

[NeerajGargi]

@MattB_Motive have you heard anything from support team about the issue ?

[MattB_Motive]

Still working through it with Support. I'll post here when a solution is found (or Microsoft fix the control).

Other users have also confirmed this happening.

[Jos_Vondar]

Hello,

I have the exact same issue with a user, with the Power apps grid control. The field is not being populated by a JS function though. It only affects them, I have tried replicating the issue with several test users but I haven't been lucky. There are two other people in his team, with the same security groups and the same roles but they aren't affected. I'm guessing it has something to do with this control but I can't be sure. If you find a solution please let me know.

[MattB_Motive]

Hi @Jos_Vondar 

Sorry to hear you're having a similar issue. Is it also a duration column?

Unfortunately, I am still trying to work through the problem with Microsoft support. Everything seems to point to it being an issue with the grid control itself rather than any JS or configuration on our end.

It might be worth submitting a support ticket for your issue as well. This might get the product team to look into it faster.

@jasongre - has this support ticket made it to you (Support Request ID: 2402030030000238)? Has there been any progress on identifying the issue?