How are content type-based structures configured?
The following example will show you how to configure structures based on content types.
This is how it works
Add content types. Content types can be used as main and sub nodes in a structure. The procedure for adding content types is described in the documentation of d.velop documents for Microsoft 365 in the chapter Adding a content type to a structure node.
Define the Relation fields.
When using content types as main nodes, specify the link fields at field (parent) and field (child) as managed property. Be sure to assign this link field to the view (see below).
Create views for all content types used (main and sub nodes).
The creation of views is described in the d.velop documents for Microsoft 365 documentation in the chapter Creating a view for a content type.
Assign the link fields in the display definition.
It is not necessary to check the link fields under Display.
Define the Storage location for documents.
Example: The customer documents are to be stored. The upload library is located in the same site as the list item with the customer record. The following configuration leads to the desired goal:
The following parameters are maintained in the Storage location for documents area:
Site collection: ${site.absoluteurl}
Site: /
Library: Customer documents
Note
Currently, a structure can and must be applied exclusively to one site. If a structure should also be valid for other websites, it is necessary that the ID of the structure be passed as URL parameter roid when calling up center.
When jumping from the sidebar this is done, with the search (search.d-velop365.com) this can be configured. Unfortunately, this is not possible when jumping from SharePoint lists with the button, because a button cannot be configured.
Note
If you want to sort items by a specific field, consider the conditions of the search service.
Only fields that are also marked as sortable in the SharePoint's search service (/_layouts/15/searchadmin/ta_listmanagedproperties.aspx?level=tenant) are sortable. Since the search service API does not share this information, make sure when configuring that sorting is only used for fields that can actually be sorted. The Refinable... fields, which can be assigned their own crawled properties, are also used for this purpose in the search service configuration. After the search service has performed the indexing, you can use the Refinable... fields for mapping.
If you use sorting for a non-sortable field, the search may return an error on the search service side and therefore the search cannot be performed. It can also happen that the sorting works in one direction, but not in the other direction.
Please also refer to the chapter What to consider when configuring SharePoint search?
Note
The assignment must be completed at each level.
Example structure in composer:
1) Customers
2) Orders
3) Orders
4) Order confirmations
In the example, you create the view and the assignment for the orders on nodes (2 + 3).