We have a property defined as a table type with a prompt list, where the values displayed in the UI differ from the values stored in the database table.
However, when we use this same property in Insights, it displays the database values instead of the corresponding prompt (display) values. We believe this might be because Insights queries the underlying table directly rather than relying on the Report Definition.
Looking for any suggestion to overcome this problem.
v25.1
This looks like an Insight reporting limitation rather than a property configuration issue. Prompt List controls resolve the display value in the UI, but Insights may still read the underlying stored value from the reporting source, so the database value appears instead of the prompt label.
The usual workaround is to expose a separate reporting field that already contains the display text, for example by using a Report Definition calculation or a mapped/calculated property, and then use that field in the Insight. That is more reliable than expecting Insight to resolve the prompt mapping automatically.
Ideally, the property should be sourced from the data page instead of Prompt list. The Report definition should also read the values from the database. As you said, Insights always reads the data from the database