Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Value Type <Anything> is interpreted as String which leads to "Data is missing a number field" #173

Open
MaddoJP opened this issue Nov 22, 2024 · 1 comment

Comments

@MaddoJP
Copy link

MaddoJP commented Nov 22, 2024

Affected Versions 5.0.0 and 5.1.0

If the Value Type is "", the attribute is interpreted as String in the new versions 5.0.0+
Value Type is used when AF Link is active.
This leads to interpretation of the values as String and not as e.g. Float thus leads to "Data is missing a number field".
If the Value Type is set to e.g. "Single" it works perfectly fine.

Please fix this.
Screenshot 2024-11-25 075558

@complacentsee
Copy link
Contributor

I'm not sure there is a perfect resolution for this. In the v4 side of the plugin, this likely worked because the javascript side of the plugin just resolved to a type at the end. With the backend being in go, we transmit this as a dataframe, which requires a field to have a concrete type https://pkg.go.dev/github.com/grafana/grafana-plugin-sdk-go/data#Field

It could be possible to allow a per query override to try to force an anything to resolve to a type. But it would need to skip not convertible values, or return nulls. Today the plugin defaults to returning nulls, as that produces trend lines most similar to how PI System Explorer would.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants