Resolving problems when developing message models

This topic contains advice for dealing with some common problems that can arise when working with message sets.

Message definition files:
Other:

Your message definition file will not open

A message definition file error is written to the task list

Your physical format property values have reverted to defaults

You are unable to enter text in the Message Definition editors

Objects in your message definition file are not listed in alphabetical order

Error messages are written to the task list after you have imported related XML schema files

A group contains two different elements with the same XML name in the same namespace

You are unable to set up a message definition file to include a message definition file within another message definition file

You want to make the Properties tab the default tab in the Message Definition editor

Error message BIP5410 is issued because a union type cannot be resolved

Error message BIP5395 is issued because an xsi:type attribute value does not correspond to a valid member type of the union

Error message BIP5396 is issued because a data type does not correspond to any of the valid data types of the union

A union type contains two or more simple types that are derived from the same fundamental type

A list type is based on a union that also contains a list type

A union type contains an enumeration or pattern facet

A deprecation error is issued on an imported .mrp file

Your imported message set looks like a simple project

User trace detects an element length error