I’m facing an issue with a Data Type in Constellation 25.1.3 and I’m wondering if anyone has experienced something similar.
I have a Data Type where I created a Text property called QuantitativeName. This property is configured as a calculated property and uses the value of another property, QuantitativeCode, which is populated while the user fills out the form.
When I save a record, both properties (QuantitativeCode and QuantitativeName) are correctly persisted in the underlying database table. I have verified that the values are stored properly.
Has anyone encountered a similar behavior with calculated properties in Insights? Is there any known limitation related to calculated fields, reporting, or Insight indexing in Constellation?
Any suggestions or alternative approaches would be greatly appreciated.
Thank you for your suggestion. However, this solution does not work in my case. When I enable Change Tracking, neither the table nor the Insight works correctly. If I disable Change Tracking, the Insight does not work either.
At the moment, I am unable to get the Insight working regardless of whether Change Tracking is enabled or disabled.