SeaTable Version {“version”:“5.1.9”,“edition”:“enterprise edition”}
Describe the Problem/Error/Question:
In my base I have a link column. From this I look up a field, namely “Kunde Link”. This column doesn’t have values in an app which uses this table, see screenshot (red). It also doesn’t help to “convert” the link from the lookup into a text by a formula; this column is also empty in the app (blue)
Is this a known limitation, or do I do something wrong?
the screenshot illucidates that the original link column, the lookup column and the formula parsing the field name as string are not hidden in the database (top half) but none of them has values in it in the app (bottom half).
OK, so your real problem is that the link column does not contain any values. (If the link column does not contain any values, it is internally consistent that the columns based thereon are also empty.)
Please check the settings of the link column. You can also modify the display value in the link column as a test.
How did you manage to lock the link column in the app, while keeping it unlocked in the base?
Found out that in App’s “Standort” column doesn’t display a thing when, in the corresponding base column, a formula field (concat of multiple columns) is selected, whereas displaying a single text column works. This would also explain why both the link formula column and the inside-table-formula column (which I tried as workaround since the link formula doesn’t work) don’t display a thing.
I’d consider this a bug. This would mean that formula fields which concat info from multiple columns are unusable in an App.
On locking the column in the App, see this screenshot, I thought this is just how it’s supposed to work. Since one can’t “lock” a column in the base, no?
In the Base there’s no problem, now the calculated values from the formula field are displayed. But in the App they don’t show. I should mention that inside the linked table I use nesting inside the table’s records, i.e. there is a parent and child entries, no deeper.
Thus it’s no bug but a feature, namely SeaTable’s nesting level limit, right?
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.
