Text-previews have disappeared from collapsed âText, Single Columnâ blocks â Most (if not all) other blocks have some sort of preview when they are collapsed. Without this feature, it can be difficult to efficiently edit some pages, especially those that are more complex.
When we first switched over to DATO in March, this feature was available, but at some point in June or July, this changed.
Thanks for reading,
MaryPat
Hey @mphofer! Happy new year 
Is the âclassâ single-line text field in that block new?
It seems like where a block contains both a multi-paragraph text field and a single-line string, weâll get the preview from the single-line string instead, with no option to override it 
This â the ability to choose which specific field gets used for a block preview â might be a nice feature request? â Feature Requests - DatoCMS community ?
Otherwise, there is also a workaround you can do:
If you convert the âclassâ field to a multi-paragraph text field instead, then it wonât have priority anymore, and the block preview should go back to the text field instead. There shouldnât be any data loss when you do that, and the API response for the developers should still be the same.
(You can test this on a forked sandbox environment first if youâd like!)
Does that help?
Hope you all are doing well there
All I know is that the preview text used to appear without having to do anything extra. The âclassâ may have popped up when something else was fixed/changed. I donât really work in that part of the site too much. This comes up when I edit more complicated pages, as itâs easier to see a bit of the text than to have to keep opening & closing the blocks.
I will run this by Kate & Pete, as theyâre more familiar with this. 
Itâs possible that field was added by somebody, and this was an unintended consequence (on our part) Sorry about that!
It should work, but feel free to have them get in touch with me too if thatâs easier! Sorry for the hassle
@kwebbink: Hi! Good to hear from you both
PS in devspeak, the Preview algorithm will prefer single-line text strings over multi-line fields. If you make the class field a multi-line one, that shouldnât change the API output, but should allow the other field (text) to be used in the Preview again. Sorry for the hassle.
Good to hear from you, too, @roger !
Thanks for suggestions â weâre checking into it.
& had a related feature request here: Ability to choose multi- or single-line text field for Block preview
Awesome, thanks! Iâd vote for that too if I could Not doing dev yet here so not something I can implement myself, but hopefully in the futureâŚ
