You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed NextCloud tables and the NextCloud Analytics extension. I created a Table with sixteen columns. The first column is Date, and the next sixteen columns are water sample types (ex. lead, mercury, iron, etc.). I then created two rows of two type of water sample readings. From there, I went to Analytics extension. Created a new bar chart using real-time data from the NextCloud table. The chart is created but the X,Y are incorrect. The Y should be the date and X should be the different column names. I have looked all around and can't find anywhere on how to define what the X and Y axis should be. I'm not sure what I'm doing wrong. Any suggestions?
The text was updated successfully, but these errors were encountered:
Hi,
some background: Currently Analytics is based on a key figure fact table - meaning the dimentions (of your chart in this case) are in the rows and not in the columns. if the table would have multible lines per date, with the categories in the second column plus the value in the third, it would work out of the box.
But I see the case here. makes sense to find an alternative display here. I will check
I installed NextCloud tables and the NextCloud Analytics extension. I created a Table with sixteen columns. The first column is Date, and the next sixteen columns are water sample types (ex. lead, mercury, iron, etc.). I then created two rows of two type of water sample readings. From there, I went to Analytics extension. Created a new bar chart using real-time data from the NextCloud table. The chart is created but the X,Y are incorrect. The Y should be the date and X should be the different column names. I have looked all around and can't find anywhere on how to define what the X and Y axis should be. I'm not sure what I'm doing wrong. Any suggestions?
The text was updated successfully, but these errors were encountered: