1 of 1 people found this helpful
Is the issue specific to ProcessBook only or all clients? Which version of PI ProcessBook are you running?
ProcessBook caches some values, have you tried disconnecting from the PI Data Archive and reconnecting (File > Connections ...) ?
Are you seeing the actual Set # or an offset? If it is an offset, you may be running into the issue specified in this KB https://techsupport.osisoft.com/Troubleshooting/KB/KB00280
Is the issue only on your machine or any machine that uses the same version of ProcessBook connected to the same PI Data Archive?
2 of 2 people found this helpful
I've seen this feedback several times and I think I've seen a bug written up for it. I'll check to see what the status is and make sure it gets considered for the next release.