Columns displayed for an object in Insights

Hello All,

I am looking for some additional details related to Available Fields for an Object in Insights. We are using 24.2.2 Constellation.

When i select a particular Data type object in Insights, i initially see few fields shown in the Available fields block and a link saying “more fields”. When i click on the more fields i see all the other fields as well. Fine till here..

Now, the question is on what basis these first set of fields are populated on the UI ? Because these are the same set of fields displayed as columns in the popup window, when user clicks on the “View Data” option for the report.

If i want to show fewer or more columns in this popup, i do not see any option to configure them. Moreover, this initial set of fields seems to be different for various data types. I mean i dont see any pattern here.

coming from Primary Fields - No

coming from Hide option for column in report definition - No

Then what else is controlling this list population

I noticed that the JSON response going back to the UI has all the fields returned from the RD. So, there should be something on the UI at runtime which is controlling this.

Attached are the snapshots of two different data types for reference where i see different number of fields on the initial load.

Wanted to know if this columns to be displayed in the “View data” popup to be configurable ?

Appreicate your patience to read through the whole content

@Kamil Janeczek @MeghanAtkins @SidduAdusumalli Need your help here

The link for Insights https://support.pega.com/discussion/ask-expert-reporting-explore-data-and-insights-meghan-atkins-and-siddu-adusumalli? is amazing and gives a very good detail.

Thanks

Jayachandra

@JayachandraSiddipeta , if it’s a Constellation application, that list is backed by Primary Fields of the object being explored.

Can you please check again? Please note that Primary Fields are cached to browser tab. For any changes in Primary Fields to reflect in Explore Data, you may need to close the browser tab with the Explore Data page and open it afresh to clear that cache.

Hi @JayachandraSiddipeta

The initial set of fields display (before selecting the more fields option) uses primary fields. If the primary fields are not setup for that class then we fallback to the fields on the Report Definition backing the Data Page used to source the Insight.

When selecting “more fields” we then show you all fields that are both marked as Relevant Records and Optimized for Reporting.

Note, that when we show Primary Fields we are only showing top-level scalar primary fields, so fields coming from a Page or Page List are not shown there… we surface those fields differently in the Available Fields UX.

Regards,
Meghan

@SidduAdusumalliMany thanks for the quick reply. Yes, Indeed the Primary fields were cached. When logged off and closed the browser, we were able to see the primary fields getting reflected.

Appreciate your support

Thanks

Jayachandra

@MeghanAtkinsThanks alot for the quick response. Yes, my initial impression was about Primary fields being used there. Because of the caching issue i could not understand why it was not working. Saw siddu’s reply and tried the same. Its working now.

Thanks

Jayachandra

@MeghanAtkins Hi but when I am trying to add the embed page as primary field those are fields are not showing up in the drilldown report.

Please find the screenshot I have added my embedpage as primary fields

@VIJAYADARAM As Meghan mentioned, we only consider top-level scalar primary fields in this scenario.

@MeghanAtkins I marked some fields as Relevant Records and Optimized for Reporting but not able to see it in Explore Data right away, even after log off and log back in. But after about 1 hour I checked again those properties are available to use in Explore Data. Is that expected or something I can do without the waiting.

@SongL17381216 Hi - that is expected. We cache the fields in the browser, so clearing your browser cache or using the browser in “incognito mode” would also fix it for you. Logging out and then logging back in won’t trigger the browser cache to clear.