I have created an Insight with several columns, and I noticed that the first two columns are displayed as links. I checked the column configuration and the Format option is set to None, yet the values still appear as hyperlinks.
Is there a way to remove this behavior? I would like these fields to be displayed as plain text rather than links.
What is confusing is that I have two different Insights: in one of them, two columns appear as links, while in the other, only one column does. I’m not sure what determines whether a column is rendered as a link or not, and how this behavior can be controlled.
Has anyone encountered this before or knows what configuration drives it?
Thanks in advance. I would really appreciate any suggestions or guidance.
The UI automatically renders a column as a link when the underlying data response includes specific metadata “key” properties that Pega uses to construct a navigation URL. The triggering properties depend on the object type:
Case objects → pxObjClass, pzInsKey, and pyID Data objects → pyGUID (or parameters defined in the data designer) Assignments → pxRefObjectKey, pxRefObjectClass, and pzInsKey
This is also why the behavior differs across your two Insights — one report’s data source includes those key properties while the other only partially does, resulting in a different number of linked columns.
How to get plain text instead
A few options depending on your setup:
Mirror the value with a calculated property — Create a calculated or secondary text property that mirrors the value you want to display. Since it lacks the key metadata, Pega won’t build a link from it. This is the cleanest workaround.
Adjust the data source — If the Insight pulls from a Data Page, you can exclude the key properties (e.g., pzInsKey) from the response for that specific Insight. No key properties = no link.
Check the column config for link toggling — Look for a setting like “enable link to the key” or “open the object” in the field/column settings. Some configurations expose a toggle for this behavior directly.
Use non-key properties — If possible, surface the display value through a property that isn’t a primary identifier, so Pega has nothing to anchor a URL to.
The calculated property approach (option 1) tends to be the most reliable if you can’t easily modify the data source.
Hope that helps unblock you — let me know if you want to dig into any of these options further!