Include "Date created" and "Date mapped" fields in factsheet search results
We are looking into reporting metrics on specific factsheets data, and in that, one of the key attributes is when the factsheet (Factsheet A) got created (date created) and when it gets mapped to another factsheet (date mapped to Factsheet .
While the date created and date mapped are available as part of the audit information, they are not available to include in search results. Can these be configured to expose for search, atleast between Factsheet A and Factsheet B?
Page 1 / 1
Hi @Ranjeeta
The Created-at date of a fact sheet is available as a field. You can add it to the table view as a column.
The creation date of a relation is not available as a field, but you could add it to your data model as a field on the relation itself, and then run an automation that sets the field value every time a fact sheet relation is created or switched to another fact sheet.
Thanks Thomas, this helps, and I see created at attribute.
w.r.t. creation date of a relation, there is “active from” and “active until” for the mapped factsheet. Is this by any chance cerate date of relation?
if not, and we go with adding the relationship field, can this field be updated with historic information through the automation?
Hi @Ranjeeta, the “active from” and “active until” fields are always filled manually and are intended to represent the validity period of the relation, not the creation date.
Regarding the automation: Updating the field with historic information is possible, I have already written similar scripts before. Depending on the number of fact sheets in your workspace, the script might run for quite some time, because it needs to process the event log for every fact sheet, but from a feasibility perspective it’s perfectly possible. If I was to write such a script, I guess I would use Python in an Azure function.
If you don’t need the timestamps to be updated in real time, you could just schedule this script like once every day and you’re done.
Thanks for the response, Thomas. will explore the option for our purpose