Have a tag with a dataset value, not sure how to be able to extract specific columns and rows for display in the report function's tag history query.
When hoping to accomplish similar things with a tag history property binding I simply bind it to the tags value at the wanted column + row, such as
[default]tagname[14,3]
I am assuming I would interface the same way in the tag history query but currently that doesn't work, maybe it is an issue with it only recently having tag history enabled however
Also, is there a way to bring information in this way in the format of [x,1] so it shows every row in column one? Or is this not a function of the reports history query?
You tagged this perspective but you keep using the word 'report'.
Can you post a screenshot of exactly what piece of UI you're interacting with, so we can align on terminology and make sure we're not leading you astray?
Oh yeah shoot shouldn't have been perspective.
I want to do this in the report function's data tag history query:
The tag I am working with is a dataset tag with history enabled:
The dataset looks like:
I want to be able to pull in specific row and column locations and historicize them using the reports history query so I can show their changes over time on a chart.
That's going to be...difficult. Enabling history storage on a dataset does nothing to help you disambiguate in the internal values, and is basically never going to be useful to you. You'll have to use scripting to "post-process" the datasets you'll get out of your raw history query to turn them into regular flat data that the rest of the reporting module is able to handle.
Any good places to start with that? The scripting in the reports is very confusing, or are you saying I need to script on a derived or reference tag?
You would have to add a script data source.
That data source would have to go through each row returned by your history data source (or you could directly run system.tag.queryTagHistory in your script). Then you'll have to go through every returned row and unpack the specific values you care about in each historized dataset, using those to build your own dataset(s), one column/dataset for each value you care about, then set those as new data keys to use them inside the actual report designer.
Or would it be easier to instead bring the info in as a single tag per column (if that makes sense)
For example the dataset is currently whatever number of headers (test type, test result, color grade) would it be easier to fill or write a tag for each header? So a tag for Test Type and then one for result and so on?
sounds miserable, I'll get to figuring that out thank you haha.
