Dynamic objects are instances of dynamic types that have been declared to the server model interpreter. Because dynamic types are known from the server model interpreter, dynamic views, as well as Rogue Wave ViewsRogue Wave ViewsScript script functions, can use them as if they were static types.

Accessors to attributes and relations are basically implemented by the class IlsDynObject which transparently accesses the corresponding element of its internal structure.

Subtypes of the class IlsDynAttribute use the Server modeling classes to implement an entry, a derived or a simple attribute, while subtypes of the class IlsDynRelation use Server relations to implement a relation following the specified semantics.

Inverse relations stored in dynamic objects are automatically maintained, unlike inverse relations that mix static types and dynamic types. (See Maintaining Inverse Relations.)

Note that there are no dynamic entities. Identified objects can be stored in a dictionary and act as a model root. If you want to have dynamic objects that can be used but not be owned, you must turn off the integrity-check mode. (See the static member function IlsModel::SetIntegrityChecked.)