Hahnming Lee
My feedback
-
21 votesHahnming Lee
supported this idea
·
-
36 votes
An error occurred while saving the comment -
18 votes
An error occurred while saving the comment Hahnming Lee
commented
This seems like a recipe for a lot of data confusion. Like if it's event-triggered with no data, you would still want a default value written? Wouldn't that effectively be just replacing the error value like Calc Failed with a #? All users would think of it as the sam, and if the value is valid, how would you know?
It seems like the underlying idea would be to be able to better account for error handling? Not sure what form that would take, but something that would likely happen before a data write.
-
9 votes
An error occurred while saving the comment Hahnming Lee
commented
Is this a troubleshooting mechanism for Notifications? Have you looked into the Notification history (2012 or earlier) or the Event Frame annotations (2016 R2 or later)? It wouldn't seem productive to provide a list of failed Notification sends (if it indeed failed) as if it can record the failure, it should have just sent. So I'm curious if this is a deficiency in the product functionality (in which case a TS case might be best to address it) or a deficiency in the product feature set.
As for manually sending the Notification, I'm also curious what this would be. Are you saying that the Event Frame is already created, but you want to send out a Notification based on it at any given time? Is this to address the failure of sending or just as a manual resend based on an administrator's preferences?
-
8 votesHahnming Lee
supported this idea
·
-
4 votes
An error occurred while saving the comment Hahnming Lee
commented
We have a YouTube playlist that looks like it covers almost all of these requests, I believe. Have you checked it out?
https://www.youtube.com/playlist?list=PLMcG1Hs2Jbcs43wQ2qO2dxW72PqGhZjKW
-
22 votes
An error occurred while saving the comment Hahnming Lee
commented
It sounds like this may actually be a request about the creation of the Event Frame rather than the sending of the Notification. Or is it both? Also, if historical EFs are getting created, why is the preference to receive an e-mail instead of just using a client tool to look up the history?
Where? Are you just looking for something that alerts you when two analyses are writing to the same place, regardless of where it is in the database (or even server)? Is this a common scenario for the customer, or do they do this unintentionally during configuration? If it's unintentional, what is the common path to getting into that scenario?
You can get a higher level look at your analysis via PI Builder and pulling in attributes and analysis. This will give you all the PI points data reference string configurations associated with attributes. While this won't exactly map it together, you can look for duplicate config string (or tag references) across attributes.