In addition to the regular data that is available in your models, you can include collections (externally managed data) and data blocks in a connection to exchange model information.


Collections (with entities and links) are model data that is externally stored and managed on a server. This data can be created using the BiZZdesign Open API and be disclosed to model packages in Enterprise Studio. The external data is organized in collections. These collections form an additional source of data next to the regular models in the model package. A model package with collections has a separate "Collections" folder , containing the collections that are available for the model package.

Data blocks

Data blocks are self-defined sets of element attributes of which the values can be added in HoriZZon sites. The data block with their attributes and values from HoriZZon can be used again in model packages in Enterprise Studio. For example, in color views and charts, but also for data exchange via one of the available connections. The data block attributes with their values are available in a model package the same way regular attributes are: in the Properties window of an element.

Using collections and data blocks in a connection

Collections and data blocks can be used in each of the available connections: Excel, ServiceNow, SQL, and Kibana.


A collection, or a container within it, can be set as the model context (scope) for a connection. The model context is set in the properties window of a connection. When using a collection as model context, please take note that its data will only be included in an export. Externally managed data is excluded when performing an import. you will also be informed about this with a message after you have selected a collection.

Collection as model context for a connection

A collection set as model context in an Excel connection

If you want to set a model context in a mapping relation that must override the general model context of the connection, you can also use a collection (or underlying containing element), but only for the export. A collection cannot be set as model context for looking up objects nor as model context for creating objects. Both are import mapping options. A collection can only be set as model context containing objects to export, an export mapping option.

Collection as model context for a mapping relation

Model context export mapping option in an Excel mapping

The objects and relations in a collection (entities and links) behave like any regular objects and relations in the model package and can therefor also be used for adding metaobjects and metarelations to a connection. Simply drag an object or relation from the collection in the model browser onto the canvas of the mapping.

Data blocks

When data blocks with their attributes and values from HoriZZon are available in the model package, they can be used in the meta-elements of the mapping to exchange data block information. Just like with the attributes of regular objects and relations, attributes from data blocks can be used by adding an attribute to the meta-element and then selecting a data block attribute.

Use of data block attributes in a mapping

Use of data block attributes in the metaobject of an Excel mapping