AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No Status
Product AVEVA™ PI Server
Categories Notifications
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Allow dots in JSON property names when using REST Delivery Endpoints

When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to allow escaping it with a backslash or even better (IMHO) to use the JSONPath way to solve this: being able to specify arbitrary property names putting them between brackets and single quotes: ['prop.erty'].
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Another way to overcome this limitation would be an option to construct the raw request body in a similar way we can construct an email body. This would also allow to use other content types (like XML) and the use of dynamic property names (linked to attribute values).
  • Guest
    Reply
    |     Aug 20, 2022
    per KnowledgeArticle "String attribute are parsed to a number for REST web service", a similar problem exists with JSON property values that can be mis-interpreted as numbers. Please expand this request to include a "clean" method of dealing with this, perhaps by allowing the user to select a data type for the value being relayed to the JSON body.