Items inside all of my listview components are not showing no matter what the source is array or database. Even standard template (AI Chat) is not displaying messages inside thelistview correctly.
My listviews are inside different containers and few of them are in drawer.
Anyone else experiencing a bug where listViews aren't displaying data properly? I'm experiencing this in multiple apps.
They were all working fine until this morning, when they (apparently randomly) just stopped displaying any info. Instead, I just see the option to "Add components", when I can clearly see from the component tree in the left sidebar that all the components I've previously added (e.g. select boxes, radio groups etc.) are still present in the listView and all have valid values, but just are not being displayed. Here are the screenshots.
I haven't changed anything that would affect any listView - the data sources for the various list views are working properly and returning results exactly as they were last night, when everything was functional. In fact, I've tried deliberately changing the queries to be wrong, which causes the listView to have a red border to indicate that there's something wrong. When I revert my queries back to their original state, this border goes away, indicating that the data is in the correct format etc.
I'm setting the value of each component using item - e.g. {{item.id}} or {{item.response_data}} - and while this gives the right value (see screenshots below for component called text2), the component just will not show up; the listView stays stuck displaying "Add components".
I have no idea what's going on. Is this just a bug? As I say, it's affecting multiple listViews across different apps in exactly the same way.
A further issue, which I suppose could be related, is that I'm not able to access {{ table1.selectedRow }} today, even though I've been doing this on tables throughout my apps up until now. It again just randomly stopped working today.
Hi @Vitor_Alano Welcome to the community! Our on call team is currently working on shipping a fix. For the time being, please see above for the temporary solution of disabling widgetgrid