Best way to present read-only data to end-users

[MattLB]

I am using a detail screen from an in-line list and I do not want anyone to be able to edit the data unless they go to an edit screen.

Is there a way or a best practice on how to display data that is read-only. What I really want an option flag for the component so it can be viewed only and not changed!

For example, I have a boolean that shows up as a nice switch BUT the end-user can change this. I want it display only (as well as other fields).

Am I missing something?

TIA

[MattLB]

OK - LITERALLY the only component I didn’t try was ‘Table’ (which I am now testing) which gives me an ugly but read-only view of the data.

Any other options??

[Darren_Murphy]

You can build your own tables using a bit of Markdown or HTML in a template column, and then display it using a Rich Text component.

Here are a few examples:

Basic Table Component

I’d probably create an HTML table for this. It goes something like… create a template column that creates a <tr> row for each legend item, eg. <tr><td>ICON</td><td>NAME</td></tr> create a Joined List column to string all those together - with no separator create a template column to insert that joined list inside some <table> tags, eg. <table>{joined-list}</table> then display that in a rich text component If you want to get fancy, you can use a CSS table generator and come up with some…

Rich Text > Actions!

Sure! One thing that isn’t obvious from the screen shot is that two of those tables are collapsable: That’s done in the usual way, using HTML <details><summary> tags. Although getting it to play nicely with the tables was a bit fiddly. Anyway… I used HTML Table Styler ▦ CSS Generator | 𝗗𝗜𝗩𝗧𝗔𝗕𝗟𝗘.𝗖𝗢𝗠 to come up with the basic table structure and CSS, and then butchered the CSS until I got it looking how I wanted. My CSS-fu is not very strong, so I suspect there is a lot of bloat the…

[MattLB]

I would prefer a read-only switch under options but this is a really good way and fits with the ‘Glide way’ of using rows as a means of storing display options like with templates. I use them for creating captions for card lists, etc.

Thanks for another tip!