Avoid to use properties for dynamic values, instead use sections.

Dynamic properties and sections are resolved at request time.

Since version 56.2 0 there is additional tooling to support use cases with dynamic properties when used with special controls. Still dynamic properties should be used very carefully. For more information please visit

The value of a document property must not be dynamic. A dynamic value is a value that is calculated at page request. This is the case for instance if you use the Display Table Macro or the Display List Macro as part of the property value.

Why is this so? Since the property value is added to the Lucene Index to enable users to search for it, a dynamic value would have to be updated whenever a new document is added or an existing document is updated. It has to be checked, whether this new or updated document is part (or no longer part) of the result set of each dynamic value of each document. The projectdoc Toolbox does not do that.

There is a limited support in case you update information from a child or parent document. In this case the existing page is reevaluated and the updated values are written to the Lucene Index. But this may fail in case of a refresh / rebuild, where the proper order of document indexing is no defined. Therefore it is recommended not to use dynamic macros as property values.

If you need to present those values on a page – you just need to display the value but there is no need to find the document with a query – there is a workaround: Just add the value to a section or content marker in the document body outside the properties table and hide it.

The query (for instance using the Display Table Macro) allows to specify property names as well as section titles in its Select Clause.

With version 56.2 0 you may also chose to use the