This is a post to hopefully help someone else if they face a similar problem.
When I upgraded to WaterGEMS Connect 10.02.01.06, I had a problem where my SCADA signals were no longer being recognized. Symptoms varied depending on how I tried to troubleshoot (sometimes no data would show, sometimes data that was clearly wrong.)
After investigating the 'View SCADA Logs' results in the SCADA Signals menu, I discovered that my old query was not being interpreted the same way. Changing the query fixed the issue.
The old query (with linebreaks added for ease of viewing):
set rowcount=5000, samplingmode=rawbytime select Tagname,Value,TimeStamp,Quality from ihRawData where (@requestedsignals) and (TimeStamp>=@startdatetime) and (TimeStamp<=@enddatetime) and Quality = "Good NonSpecific"
The new query:
set rowcount=5000, samplingmode=rawbytime select Tagname,Value,TimeStamp,Quality from ihRawData where (Tagname=@requestedsignals) and (TimeStamp>=@startdatetime) and (TimeStamp<=@enddatetime) and Quality = "Good NonSpecific"
The problem seems to be that the @requestedsignals variable used to expand out to include the fieldname=tagname, but now just expands to show the tagname. Adding 'Tagname=' fixed the issue.
Note that if @requestedsignals was expected to return multiple values (which it looks like it can, I'm not sure under what circumstances it would), I would experiment more with the query to use "IN" rather than "=", and probably move that outside the parentheses.
More details on how I've set up my SCADA signals to work with Historian can be found in a previous thread. Adding the 'set rowcount=5000' to limit the results fixed the issue I was experiencing in that thread.
communities.bentley.com/.../494394
Thanks for looking into this! Our Historian version is older than yours (4.0.0.176) because we have some legacy dependencies, so that could actually be the culprit. We've got an upgrade in the works, but that's probably a ways out still.