Hi @TshililoP ,
Thanks for reaching out!
I believe the solution you’re looking for is the Conservator Description table. Conservator Description has a many-to-one relationship with Collection Object and can be added as a subview on the Collection Object form.
Conservator Events is another table, many-to-one related with Conservator Description. This would allow you to store multiple histories of Conservator/Maintenance records on a given Collection Object. In other words, you can have multiple Conservator Description records each with its own “history” or set of Conservator Events.
If that extensibility is not needed or preferred, you can also choose to store your Maintenance History as multiple Conservator Description records on the Collection Object, or as multiple Conservator Events on a single Conservator Description.
Conservator Description and Event forms can be customized to suit your needs!
Both tables contain multiple fields for agent, date, and number of other user-definable fields.
By default, the forms appear as shown below:
Subform subview:
[!Note]
Note: The “Collection Object” field should be removed from theConservDescriptionsubview form definition.
XML for subform subview:
<row>
<cell type="subview" id="cd" name="conservDescriptions" viewname="conservDescriptions" colspan="12"/>
</row>
Conservator Descriptions can also a button subview on Collection Object:
XML for Button Subview:
<cell type="subview" id="cd" name="conservDescriptions" viewname="conservDescriptions" initialize="btn=true"/>
See our guide on Form Editing for more information:
Additionally, you can change the display names for Conservator Descriptions and Events in your database by editing the table name(s) in Schema Configuration.
I hope this helps! Let us know of any further questions.

