How can we improve OSIsoft Message Format?

Clearly state that a Data message cannot include both a container ID and a type ID

Right now, the documentation:

https://omf-docs.readthedocs.io/en/v1.0/Data_Messages.html

Mentions that "For each object, either typeid or containerid must be specified". However, it does not clearly state that you CANNOT include both in a data message, even if either the typeid or containerid is null (and the other is non-null). It's a minor distinction, but it helps prevent folks from trying to create a base class for a data message that includes both a typeid and containerid.

2 votes
Sign in Sign in with OSIsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Dan Lopez shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in Sign in with OSIsoft
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED