List View Control in Form Based Apps
I am starting to experiment with Form Based apps. I have some questions/comments about the List View control that is built when you create one of these.
Is there any way to configure column widths on the List View control? There are no options for setting column width percentages like there is on a Data Grid. Can it be done with CSS or JavaScript? The default behavior of the List View is that all fields get an equal amount of width on the screen. This does not work too well if you have long text fields mixed with shorter code type fields. The long text fields end up wrapping and it looks pretty bad.
I'm also not a big fan of how the adding and editing works where it takes you off into an entirely new screen. I much prefer how the Data Grid control works where if you edit a row, you actually edit it right there in the grid and if you add a new record, it adds it there in the grid as well.
One aspect of this that I really don't like is the scenario where a user has filtered the List View to narrow it down to a specific set of records. They then go and edit one of those records and submit the change. When the List View screen comes back up, all the filters are cleared out and the user is looking at the full set of data again. They then have to filter the fields again to get back to the subset of records they were working with to see that their change took. I assume that this happens because the List View screen is loaded fresh as if you had just launched the app. Is there anyway to pass filter criteria between these screens so that the user is presented back the data they were originally looking at?
-
Hi Loren,
Find reference to your question below:
Question: "Is there any way to configure column widths on the List View control?"
Answer: Currently no. You can choose which fields to show (and the columns label) and which will show on the mobile view (up to 4). Width will break even across the columns chosen to be displayed.

Question: "Can it be done with CSS or JavaScript?"
Answer: Yes, using CSS (or JS if preferred or both) you can overwrite the current width.
Note: "I'm also not a big fan of how the adding and editing works where it takes you off into an entirely new screen".
Refer: The GRID and ListView are aimed for different usage - the purpose of the ListView is to provide with an initial view of your Data, as a kind of a report view (and like with SharePoint lists and alike), while the GRID is more to provide with table oriented edit mode ("bulk edit").
Note: "I much prefer how the Data Grid control works where if you edit a row, you actually edit it right there in the grid and if you add a new record, it adds it there in the grid as well."
Refer: keep in mind that eventually the view form is just an eForm, so you can add a Grid control and/or a subform in addition to the ListView or instead, to get your desired view form look&feel. Another topic to take in consideration in regards, is that typically, Form Based App underlying DataSource will be a relational data sources, meaning, the parent Entity will typically have child entity in a 1:n relationship (which GRID will be limited for) and for this reson the list view provide the initial ListView and allow the drill in to the full item view using the Update Form, which can show the related items as well in a detailed fashion.
Question/Note: "I assume that this happens because the List View screen is loaded fresh as if you had just launched the app."
Refer: Yes. This is in order to the load any changes applied on the data (DataSource) from the Update Form.
Question: Is there anyway to pass filter criteria between these screens so that the user is presented back the data they were originally looking at?
Answer: Not OOTB, but can be done with some JavaScript.
Hope this helps.
Thanks,
Yaniv.
請登入寫評論。
評論
1 條評論