Schema Hierarchies (Parent and Child)

A parent/child setup becomes useful when the schemas share standard fields. In that case, you add all common fields to the parent schema, and the children carry only the fields that are different. In Picturepark the children are by default not displayed but only the parent which you can open with a double-click. You can identify the parent from the icon used images/download/thumbnails/28411990/image2020-2-25_17-32-6.png .


  • You cannot remove a field that is on the parent from a child schema.

  • You can only reorder the fields that are on the child directly. You cannot reorder inherited fields. The parent fields display above the child fields.

  • You can break inheritance for tagboxes but not for other fields. As an example, you can set the title required on the parent and inherit this setting to all children, having the title not required in this setup is not possible.

Parent-Child support will be removed for Fieldset and Relationships.

Child Virtual Types

Virtual Types can be nested, which enables you to think of them in a hierarchical manner. This nesting is beneficial if you use several Virtual Types that should share some information.

For example, say you use Picturepark to publish job listings, news items, and partner listings. Each Virtual Type is different, but there are a few pieces of information you want to make sure are included wherever the information is published:

  • Copyright Notice

  • Impressum Link

You add these values to "Company Publishing" Virtual Type, and when you create children, they have fields for a copyright notice and Impressum link always available. The default values included in the "Company Publishing" Virtual Type would then be included automatically with all other Virtual Types created in Picturepark.