Hi,
I have a state timeline set up with a couple of columns, but some data is not showing.
When I switch to the table view when editing the panel, the row with the information I am trying to display is right there, so it loads, but when I’m trying to show it as a new section in the timeline, it disappears.
I can make it appear by using the “organize fields by name” panel, if I disable all columns apart from this one that contains the data.
I get the data from sqlserver via a procedure, but I’ve tried json from an api as well and it’s the same.
Here is 2 columns displayed:
And here is when I disable the second one remaining:
This red section appears. It should be there no matter how many timelines I’m displaying, right?
I can unhide more, and no more entries disappear:
Does anyone knows a fix for this? I’ve searched the forum, but I did not find any mention of this.
welcome to forum @ignacysionek
can you please share the column names being returned by stored procedure and their data types?
1 Like
Hi.
Unfortunately I cannot quote them directly, as these are names [name surname]. The type is varchar(150). Special signs can appear, but they not present in this example.
So the data looks like:
[DataOd] datetime, [name surname] varchar(150),[another one] varchar(150), and so on.
This is generated with dynamic SQL.
I can see the data no problem in the table (also in grafana). State timeline also displays them when limited to a single column (limiting to one column sql-side has the same effect as limiting to one in the visualization).
so data might look like
dateOd,[Diego Maradona],[Kylian Mbappé],[Vinicius Junior],[Yamil Lamal]
2025-06-02,3,35,23,7
More precisely:
dateOd,[Diego Maradona],[Kylian Mbappé],[Vinicius Junior],[Yamil Lamal]
2025-06-02 09:02:11,‘text’,‘other text’,null,null
2025-06-02 09:13:36,null,‘something’,‘text’,‘text’’
Not everyone has all dates associated with some data point in time. One way to contextualise this would be to say “the data tells you what someone started doing something and when”. [DataOd] still has all the possible datetime values (so there are lots of nulls. I think these null values aren’t a problem as SQL filtering (so no nulls are present and we only get a single column) has the same effect as filtering in grafana (when nulls remain in the loaded data).
1 Like
I’ve found the culprit.
The data reappears when pagination is disabled:
There are just 35 entries in this dataset, so 50 elements per page shouldn’t have an effect.
I have had pagination set to 50, because there are up to 300 entries (columns), so without having the max bar height (row height seems to only scale and not set the height) small amount of entries would make them too big, and a large amount would make them too small. Pagination allowed for some freedom in setting max height by making the entire visualisation smaller.
Without this option I’ll have to always have a set amount of columns to limit bar height (probably append after calculating a certain set).
1 Like
