Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

Add a new idea Subscribe
Status No status
Product Developer Resources
Categories Open Message Format (OMF)
Created by Guest
Created on Aug 16, 2022

RELATED IDEAS

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.
  • Attach files