Skip to Main Content
AVEVA™ Data Hub 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 Data Hub. For links to our other feedback portals, please see RESOURCES below.

Status No Status
Created by Guest
Created on Aug 19, 2022

Always supply millisecond component of timestamp in response payloads

OCS returns a timestamp with no ‘milliseconds component’ if milliseconds is zero. This places a (small) burden on the client application to code for both possibilities … milliseconds present in the timestamp field and milliseconds not present. This places a small burden on some clients such that they have to code for both possibilities. It would be nice to have a consistent expression of time in response payloads.
  • Attach files