• State Verified Answer
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 418 views
  • Users 0 members are here
Options
Related

Number and String value in the same input file?

Olav

Hi.

I have a UFL instance which is handling data from several different sources (same point source). It is a very simple input file which on contains the bare minimum of tag,timestamp,value.

 

However, now I need to also handle string values. Is it possible to do this within the same UFL instance? If so, how do I do it? Right now, I only have these three fields defined and one action of storing the three fields to PI.

  • 0

    Hi Olav,

    By "several different sources" do you mean that your input files contain different data e.g. temperatures, pressures but in the same format?

    I assume your field storing the value is of type "Number" and the question is how parse data that has string type as its value? In one of my recent UFL implementations I had to use string-type fields even for numeric values in combination with a PI Point of one of numeric types. Assuming that input values are always numeric, they will be stored in a PI Point successfully. With that being said, if you want to use the same instance/INI file for both types, I would suggest trying using a value field with string type.

    Please let us know if that is what you are dealing with!

  • 0 in reply to piotr.wedziuk

    Hi,

    Yes, by several different sources, I mean the files come in from different systems, but all in the same format. I am storing value with type "number". My problem is as you explain, that I now have some new PI tags which have datatype string, and I would like to handle it inside PI UFL if possible without creating a new instance/INI file.

  • 0 in reply to Olav

    Thanks for the clarification. So as I said before, I would change the Field type to string in the UFL INI file so it can store both number and strings. Then, depending on the target PI Point, it data will be stored with the respective format.

  • 0 in reply to Olav

    Hi. Finally got to finish testing on this, and it works as you suggested. Just changing the field type to string solved it. Simple and easy. Thanks.