Sriram

I think that is the expected behaviour. Even default grafana table plugin works same way. Doesn't?

Have u tried the new tag delimiter feature ? https://github.com/yesoreyeram/yesoreyeram-boomtable-panel/blob/master/README.md#tag-delimiter-for-influxdb-and-prometheus----experimental-feature-

It seems you need space delimiter as per your metric name

https://github.com/yesoreyeram/yesoreyeram-boomsummary-panel may help somehow. (Still in poc/Dev stage)

Can you attach sample data from both the queries?

Can you check if you are able to reproduce the issue after removing transformations. I suspect the behaviour of transformations.

I agree and fix coming soon. Thank you for reporting.

Just wondering how does this makes sense for the auto headers? How the plugin know the field type unless specified.. it can assume the type. But that may be error...

Hmm. formatting as string does produce the correct results for me at least [here](https://grafana-infinity-datasource.herokuapp.com/explore?orgId=1&left=%7B%22datasource%22:%22Infinity%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22type%22:%22json%22,%22source%22:%22inline%22,%22format%22:%22table%22,%22url%22:%22%22,%22url_options%22:%7B%22method%22:%22GET%22,%22data%22:%22%22%7D,%22root_selector%22:%22%22,%22columns%22:%5B%7B%22text%22:%22SN%22,%22selector%22:%22serialNumber%22,%22type%22:%22string%22%7D%5D,%22filters%22:%5B%5D,%22global_query_id%22:%22%22,%22data%22:%22%5B%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007111%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007112%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007113%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007114%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007115%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007116%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007117%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007118%5C%22%7D,%5Cn%5Ct%7B%5C%22serialNumber%5C%22:%20%5C%229921020321007119%5C%22%7D%5Cn%5D%5Cn%22%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D). But I can confirm that parsing as number for big integers causing issue with Javascript. As...

@yosiasz just tidying up old issues. Do you think still this relevant in latest grafana + latest plugin?