Question:
Can I create historic fields at runtime? Or are they only available for edition in the Studio?
Solution:
Yes, you can create historic fields at runtime; to do so, you will need to use the Fields object’s AddField method. This article illustrates how to do so.
First, you must understand what an Elipse E3 Historic is. A Historic is an Elipse E3 object that you will use for storage purposes. It is a module responsible for storing data from the application in the Database. It allows storing process data for future analyses, in Elipse E3 or any other tool available for doing so.
The Historic’s Fields object (HistFieldsCollection) was introduced at version 5.0 of Elipse E3 in order to return the collection of fields in a Historic. Since its introduction to the Elipse system, it has been possible to handle it not only in Studio mode but also at run time, which allows for greater flexibility for developing, editing and automating historic objects. You can access the Fields object via Historic’s Fields property.
For further information on Fields object, check the article Returning a Historic’s field collection by using Fields object in Elipse E3.
However, in versions previous to Elipse E3 5.0, the procedure is different. In order to add Historic fields at runtime, you can create an XObject that contains a Historic. But in this case, the number of fields must be pre-established. For each field, you can create an XObject property to associate the tags to record.
