Questionnaire App DataViewList Vs.Template Grid

Does anyone know the reason behind the Questionnaire using a dataviewlist widget vs. the built in template grid? I have a refresh issue on when a user goes to answer a question that’s located at the bottom of the page, the save action automatically refreshes and puts the user at the top of the page. I can resolve this using a template gird, but want to know if there are any issues with this approach, since the questionnaire app was built with the dataviewlist.
2 answers

Hi Julio, I had the same problem and rebuilt it with the template grid indeed. Works fine now.

I think is has historic reasons because now you can create editable template grids with the form loader, that wasn't always the case.

An other reason is possibly performance. Imo both widgets are not really efficient for doing this in terms of request they sent to the server. Maybe the dataview list is a bit more efficient. You can check that out by opening firebug to get an idea about the request volume the dataviewlist widget is sending to the server. After replacing the widget, check it again to see if there is substantial differenence.


The DataViewList is capable of rendering a different template for each specialization of the main entity. Unfortunately, the implementation in the App Store module does not use this feature and uses conditional formatting instead. This leads to bad performance.

For Mendix 5 users: In Mendix 5.3.1 we added inheritance and editability to the standard List View widget so that you do not need the DataViewList widget anymore.

See also my answer here: