Thread: Selectively exclude custom columns from single MDE
View Single Post
Old 02-03-2022, 04:59 PM   #53
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 22,116
Karma: 30277960
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by ownedbycats View Post
It's kind of an ugly solution, but what I've done before is have one column with a short label for book list/MDE use, and then have a {#yourcolumn} composite column with a nicer label for book detail usage.
Composite columns don't have a header position attribute so that's not suitable for columns such as my Blurb column.

BR
BetterRed is offline   Reply With Quote