How to refresh the data grid with microflow set as the data source

Hi there.   The data grid with microflow as data source is not updated. As a page configuration, we have a data grid in a data view and a microflow set as the data source of the data grid. In the microflow, I am getting an entity that is separate from the context through an association, sorting and calculating some attributes. For the values of these calculated attributes, there are cases where the values are not displayed in the data grid, even though the values are correct when viewed in the debugger. (This is annoying because sometimes it shows up and sometimes it doesn't) I thought I needed to update the page parameters, so I did a refresh with change object, but it doesn't change. Does anyone know of any solutions?   Thanks in advance. BR, Kazuki Abe
2 answers

Hi Kazuki Abe,

                          Method 1: Check if the data view and data grid were not belong to any kind of relations. because in page only one source can be given as parameter, I think in your case if u use 2 data containers with 1 source , the missing of attribute values might occurs. to solve this create a object and pass it directly to page.

                         Method 2: In microflow ensure that all the manipulated data’s are commited at last of the flow and enabled refresh in client. the missing of data means that the page parameter will be having those attributes has void. check this once , if it not worked update the question with Screenshots how you approached..



So the reason your data grid isn't updating when running a flow in the queue, is that the queue does not have a “client” to refresh – it's running in the background (on the server)


If you want something like client refreshes for a process that the user didn't start themselves, you can use one of two methods:

  1. The quick and dirty method: Add a Microflow Timer to your page that refreshes the page every x seconds. This is dirty because you will be refreshing often even if there are no changes to any of the objects, and it's not great for performance, but it's very easy and quick to implement.
  2. The better, but harder to implement solution: Websockets. These allow your client to listen to a server that can send a message whenever the grid in question should be updated. 

Depending on your use case, one or the other might be better.