View Single Post
Old 02-23-2026, 05:01 PM   #29
varia
Enthusiast
varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'varia can spell AND pronounce 'liseuse.'
 
varia's Avatar
 
Posts: 39
Karma: 39844
Join Date: Jan 2026
Device: Samsung Galaxy Tab S10 Lite
Quote:
Originally Posted by thiago.eec View Post
I think the must important step right now is to allow the user to use their own custom columns without hard coding their lookup name. Right now, you can choose any type of custom column in the Columns tab, even if they won't work; also, even if it is the right type, it won't work either if the lookup name differs.

Like @Comfy.n said, you can check out Reading Goal's solution. You can choose your own columns based in their data type and add a new column (respecting the needed type) if it doesn't exist.

P.S.: I'm the Reading Goal author.
I was just thinking it was a hardcoding issue. I believed you nailed this particular case and that was the intended direction I was going into while creating it. Flexibility is a must. Thanks for the input, Thiago. I appreciate it.
varia is offline   Reply With Quote