Complex Datatype Limitations

Understand complex datatype (structures) restrictions and limitations.

Complex datatype default value limitations

You can only set a default value for the complex datatype, not values for individual fields within the complex datatype.
If multiple parameters refer to the same structure object, and individual default values are set for the parameters, Unwired WorkSpace passes only the first value to the structure and ignores the other values. To avoid this situation:
Instead of having multiple parameters reference the same MBO, copy and paste the structure object so that each reference is to a single structure object.

Complex datatype limitations

Complex datatypes which are not bound to any MBO operation or component are not included in the generated code
If you create a nested tree with three levels (structures) and you delete the last node in the tree (level three), no error message displays indicating that the attribute type of one of the attributes on level two is non-existent
If there is a type mismatch between a synchronization parameter type and personalization key type, the error is not visible in the header area of the properties view.
If you attempt to model a structure with a field/attribute of the same type you either get a StackOverflowError or if you try to model an attribute type as a list type of the same structure, the change is ignored.
If you attempt to model two structures each with attributes of the other type (for example, structure5 contains an attribute of type structure6, and strcuture6 contains an attribute of type structure5) a StackOverflowError occurs.

Deleting structures

A structure can be referenced by a personalization key or a parameter or other structure's attribute. It can be deleted only if it's not referenced by any entity. If a personalization key references the structure, the deletion of the structure (either from object diagram or from workspace navigator) generates an error similar to:

"Structure type:'' < structure_name > '' can''t be deleted, 
because it is still referenced by personalization key : '' < PK_name > ''".

A Cut operation in the object diagram or Delete operation generates a similar error message if it is still referenced by a parameter or other structure.