This seems to be caused by some change in how dropdown data is saved in Grafana Segment controls. The error occurs both when a user changes a dropdown selection, for example in an Entity Data source query builder, WHERE clause by changing a label. Grafana also saves the dashboard data when this happens and this error is triggered. While the error seems to be ignored when changing the dropdown selection (i.e. the selection is still changed), when user attempts to save the dashboard it's an error that prevents the save.

The given error is part of Grafana code doing a jsonDiff in getPanelChanges() in getDashboardChanges.ts in webpack://grafana/public/app/features/dashboard-scene/saving/getDashboardChanges.ts.

Issue may be in:

targets[0].clauses[0].attribute.type or
targets[0].clauses[0].attribute.value.type

of type SearchPropertyType

where some data is expected to be a string (which has the b.replace() operations performed on it), but is actually an object with { id, label } or { i, l } or similar.

Not sure this is the issue, but just noting my findings.

Did not see anything specifically about this in Grafana 11.3.0.

We would have to do more work in order to make OPG compatible with Grafana 11, so we are closing this for now.

thanks - I’ll write up my findings soon, we’ll probably need to come back to it later when we have more resources to work on it.

Hi , there is no customer ticket associated with this issue. We discovered it in my lab. We wanted to bring this issue up.

Best regards,

Eric

is there a customer or support ticket associated with this issue? Seems there may be a small incompatibility in data structures when trying to save, but would need to spend more time on it to see if there’s a fix or not. As noted, we don’t officially support Grafana 11 or even 10 yet, though OPG seems to generally work with at least 10.

With Grafana 11.3.0+ I’m finding this same error both when trying to save a dashboard and also when updating an Entity data source query, changing one of the dropdowns like WHERE or ORDER BY. Seems to have something to do with the Json stringify code ultimately called after EntityQueryEditor, updateQuery, possibly when passed an empty array. But it’s hard to troubleshoot since the call stack is pretty deep.

We don’t officially support Grafana 11 yet. We’ll try to look into it more, but best advice is to see if customer can use Grafana 11.2.5.