Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Field keys returning from server come back in wrong order #1158
Using the first field appears to be the current behavior when creating a single stat:
For fields A and B, I first added A, then B, removed A, added A, then removed B to arrive at the initial state. It displays the first field in the query.
I think this can be closed unless someone can provide repro steps showing otherwise.
@timraymond After further diagnosis, it appears that Single Stat is behaving as expected. Given a query with two fields, it will display the most current value for the first field.
However, occasionally when saving changes to a cell, the field keys in the queryConfig will come back from the server in a different order than when they were submitted. This means that if we submit
it's possible to receive
When validating the query at
This means that you may see one stat in the CEO but another stat when returning to the dashboard.
changed the title from
Display single stat as the first field requested.
Field keys returning from server come back in wrong order
May 4, 2017
@rkuchan can we put in the known issues that single-stat graphs with custom time ranges will return inconsistent results if there are multiple fields in the query.
The work around is to use dashTime or to only return a single field from the query for single stat graphs