Best way to create an Insight combining data from two Data Objects?

Hi everyone,

I need to create an Insight that combines data from two different Data Objects.

So far, I have created a Read-Only Data Page using a Report Definition as the source. However, I’m unsure about the best approach to correctly expose properties from both objects in the final Insight.

I’ve considered and tried the following options:

  • Creating a join directly in the Report Definition

  • Using Associations in the Report Definition

Unfortunately, none of these approaches are working as expected, since I’m not able to see data from the second object in the Insight.

What would be the recommended or best practice approach to achieve this?
Is there a specific configuration or limitation I might be missing when combining Data Objects for Insights?

Thanks in advance for your help!

I would recommend using Insights and Association to pull the data from two different data objects.

  1. Create the Association rule.

  2. Explore tab → 3 dots → Clear cache

  3. Create a new Insight and corresponding association for the 2nd data object should be shown to display the records ( below screenshot just an example)

Thank you @RameshSangili for your response. I’ve implemented your suggestion, I have already created the Association and cleared the cache, but I’m not sure why the Association is not showing up.

At the moment, I can only see two options: Update Operator and Create Operator, as shown in the image.

Could you please advise what might be causing the Association not to appear?

Does the association shows in the Report definition? If yes, Could you please try logoff and login again? and then check Insights.

First of all thanks for answer, but I’m not sure what I might be doing wrong. I’ll try to summarize my issue as clearly as possible.

I created an Association called LabRound in the class of the LabRoundResults Data Object, joining it with the LabRound class, since I need to access data from that class.

Then, I created a new Data Page (List, Read-Only) with a Report Definition as the source, where I included the Association I created (all of this configured in Dev Studio). When I run the report, it returns all the data correctly, including the columns from the associated class.

After that, I switched to App Studio to create an Insight. In Explore Data, I cleared the cache and then selected Data Pages from the dropdown. I chose the Data Page I created earlier, but the Association does not appear, and I get the message:

“This data source supports a limited set of features.”

In this case, the Data Page does not have the option “Allow querying any column (Pega connection only)” enabled. However, when I enable this option and return to App Studio, the Data Page no longer appears in the list of available options.

For reference, I have attached a screenshot.

On the other hand, when I select in Explore Data the default Data Page that is automatically created with the Data Object, I can see that the option “Allow querying any column (Pega connection only)” is enabled. In that case, I can see two associations related to Operator (Create and Update). However, these associations are not explicitly added in the Report Definition of DataTableEditorReport.

My understanding is that the Object option in Explore Data is pointing to this default Data Page.

I hope my explanation is clear, and I would really appreciate any guidance on what I might be missing.

I’ve managed to find the root cause.

The issue was related to the when rule pyUseAllAssociationsForDataSet, which is disabled by default. After enabling it, it works—but only when selecting the Data Object, not my custom Data Page.

That said, I still don’t fully understand why a custom Data Page with associations cannot be used for Insights. In my scenario, it only works when I select the Data Object directly.

Is this an expected limitation, or am I still missing some configuration?

Thanks for sharing! I hope you can achieve the same through Insights without your Custom data page since you’re able to see the Associations now.

Yes, that works. However, I’m trying to understand why the alternative approach does not.