Conversation


Pegasystems Inc.
IN
Last activity: 3 Oct 2025 9:25 EDT
Accessing a personalized view of an insight
User in prod has saved as a personalized view of an insight available on Dashboard. Is there a way we can access the personalized view using Admin access on App studio or Dev studio.
-
Reply
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!


Pegasystems Inc.
IN
@pateb2 @MarcCheong For your reference.
-
Marc Cheong
Updated: 1 Oct 2025 12:37 EDT

Pegasystems Inc.
GB
@pateb2 this is a lot like the UI Kit dashboards capability, system-user data instances. In this case, for Constellation, you'll find the data instances in System-User-Grids
- There is a default one for my default
- And then instances for my saved versions
Most of the details you are after is inside the XML, its not a rule so not easily exportable or replicated.
-
Hrithik Reddy Kandewar

Pegasystems Inc.
GB
As an added bonus, for Insights, the ID matches the ID you can see in your URL or Info, which should allow you to find the personalization for a specific Insight.


Pegasystems Inc.
IN
@MarcCheongWe are running in to a production issue. Here is the scenario:
- User creates a personalized view from an insight available on Dashboard.
- Insight gets modified in a later release cycle and is deployed to Production.
- User tries to use the personalized view after go live.
- Data displayed is not accurate and is displayed as per the old insight definition.
Do we have a systematic way to address this gap as there can be multiple users with personalized views saved from previous definition of Insight.
Updated: 6 Oct 2025 3:24 EDT

Pegasystems Inc.
GB
@pateb2 what you are seeing is expected, personalization is exactly that - we give the user the choice of how their data is shown, including the default view and any other additional views they want to add to that insight.
For me, personally, I don't see the value in creating Insights in a Dev environment and Promoted these up - Explore Data / Insights is geared for self service, so we should be allow the business to produce the reports the need. As a former business user, having to wait and pay, for developers to create me a report I wanted, there is a huge value in business building their own reports. However, that said, you are where you are with your deployment model for Insights so a couple of things to consider:
@pateb2 what you are seeing is expected, personalization is exactly that - we give the user the choice of how their data is shown, including the default view and any other additional views they want to add to that insight.
For me, personally, I don't see the value in creating Insights in a Dev environment and Promoted these up - Explore Data / Insights is geared for self service, so we should be allow the business to produce the reports the need. As a former business user, having to wait and pay, for developers to create me a report I wanted, there is a huge value in business building their own reports. However, that said, you are where you are with your deployment model for Insights so a couple of things to consider:
- The developed insight view, should still be there. Users who personalize the insight to should have additional options in the menu for the personalized insight, though its not always obvious. They may have changed their default view and not even known there was other options (common).
- If you are packaging certain insights in your PROD releases, then you could look at your CICD process to help identify when this issue might arise.
- You could further look to delete personalization instances of that Insight if there is a new version.
- Though I personally feel that would cause more friction than benefit
- You could look to publish in release notes to mention to the user base that a new version of this insight exists, they should have a look at the original (which may not be their default anymore)
- You could further look to delete personalization instances of that Insight if there is a new version.
- You could go the nuclear route - delete the old insight, create a new one. Insights are easily copied via "save as", which will give it a new ID and all personalizations on the old ID will not be copied. Given its a data instance, your prod release would also have to delete it (as merge pipeline won't) and like 2.1 you could cause more user friction than benefits.
There's a chance I have misunderstood your issue, maybe the data is factually incorrect? In which case maybe options 2 or 3 would actually be a better solution. Will leave you to decide which is best.


Pegasystems Inc.
IN
@MarcCheongThanks Marc for the suggestions.
FYR @kolip
-
Marc Cheong