-
I am new to Kibana and enhanced table. Thanks in advance for helping me out! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
You just have to fill « row computed filter » setting with : given that your column is the first column. |
Beta Was this translation helpful? Give feedback.
-
Does Row computed filter works for computed column?
Because mine is a computed column and when I set row computed filter with col36 != 0 in my case it is giving me this error "Column number 36 does not exist, in Rows computed filter: col36 != 0”
… On 21-Jul-2021, at 11:33 PM, Fabien Baligand ***@***.***> wrote:
You just have to fill « row computed filter » setting with :
col0 != 0
given that your column is the first column.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#218 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKGJZK3UBWSA2ITWE4I3SLTY4DXTANCNFSM5AYKZLKA>.
|
Beta Was this translation helpful? Give feedback.
-
Waou... 36 columns! That's a lot! To answer your question: Yes, "rows computed filter" works nice with computed columns. I just verified to be sure. |
Beta Was this translation helpful? Give feedback.
-
Let me try once again yes I used 0-based index. Am using enhanced table for User Account prioritisation which is calculated upon multiple categories. Even though have numerous column I could achieve the result using enhanced table very easily. Thanks a lot to you for giving us this plugin.
… On 22-Jul-2021, at 3:40 AM, Fabien Baligand ***@***.***> wrote:
Waou... 36 columns! That's a lot!
I'm curious: you use "Enhanced Table" visualization (for aggregated data) or "Document Table" visualization (for single documents)
To answer your question: Yes, "rows computed filter" works nice with computed columns. I just verified to be sure.
But be sure that you use 0-based index. I mean: if you want the 36th column, so use col35 (not col36).
By the way, you can also reference the column by its label: col['Column Label']
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#218 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKGJZJYZVTTXTVHZPRY3ATTY5AWPANCNFSM5AYKZLKA>.
|
Beta Was this translation helpful? Give feedback.
-
Also in Cell computed CSS want to differentiate the colors based on cell value, For example if cell value is 2 I want the cell to be green color and if its value is 1 I want it to be red color so I tried the the following statement
value=2?”background-color:green”:”background-color:red”
My output was green for all the cells in that column.
… On 22-Jul-2021, at 3:40 AM, Fabien Baligand ***@***.***> wrote:
Waou... 36 columns! That's a lot!
I'm curious: you use "Enhanced Table" visualization (for aggregated data) or "Document Table" visualization (for single documents)
To answer your question: Yes, "rows computed filter" works nice with computed columns. I just verified to be sure.
But be sure that you use 0-based index. I mean: if you want the 36th column, so use col35 (not col36).
By the way, you can also reference the column by its label: col['Column Label']
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#218 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKGJZJYZVTTXTVHZPRY3ATTY5AWPANCNFSM5AYKZLKA>.
|
Beta Was this translation helpful? Give feedback.
Waou... 36 columns! That's a lot!
I'm curious: you use "Enhanced Table" visualization (for aggregated data) or "Document Table" visualization (for single documents)
To answer your question: Yes, "rows computed filter" works nice with computed columns. I just verified to be sure.
But be sure that you use 0-based index. I mean: if you want the 36th column, so use
col35
(notcol36
).By the way, you can also reference the column by its label:
col['Column Label']