MagicDraw/Cameo v19SP3: The display of units can't be disabled on the initialValues compartment for context-specific values, which can lead to inconsistencies when an OpaqueExpression that references value property names is used.

This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
Icon class
far fa-sticky-note
far fa-sticky-note
Note kind
Policy level
UML keywords
SysMLv1.x keywords
Click on the image to view it full size
The issue arises probably because of the legacy of SysMLv1.x extending UML2.5.x. Because SysMLv1.x (unlike Mathematica) does not offer a fully Units-aware Quantity algebra, it does not take into consideration that each "variable" (value property) may carry its own units. Tacking on the Unit display in this case in fact leads to dimensional errors!
Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)