We are trying to show additional details of a particular piece of information.
So it is basically a Table view that contains three columns: CustomerID, Name, and Age
So when the user clicks on the CustomerID, we need to call another data page which gives the data about the Customer Address and shows the data in a pop-up or any other way and how we can handle it in constallation
I tried to with a check Box called Show Additional Details
When I click on that, I can see two options Open View
Display as Link to Object
With Open view, I can able to see only four options
So need to understand if we can give our own customised view, which is created in the same class as the table source.
If not, how can we use these views? I am unable to find this in the system.
We have tried using Display as Link to the object, but here, how can we give the target view
@Satish_Koripalli I also came across the same situation few days ago. Tried to figure out the logic based on which it is showing only selected views, but no luck with it. But somehow got a workaround. Out of the views that are coming in the dropdown, save as one of those views with your preferred name into your class and then modify the content as per your requirement. Log off and login once and that will definitely come in this dropdown.
Don’t forget to mark the new view as relevant record once created. Otherwise it won’t come up.
It may be possible however there maybe a couple of important limits around how “Show additional details”, “Open view” and “Display as link to object” behave.
In practice, the cleanest solution is usually to model the clicked row as a data object/reference and then open a target view for that object, rather than expecting a fully free-form popup from the table cell itself
Open View lets you open one of the supported Constellation views associated with the object/context, but it does not behave like a fully arbitrary popup builder. Display as Link to Object works when the table data is object-aware, and the row contains the identifiers Pega needs to resolve the target object. For data objects, the response must include the properties required by the lookup data page, and for case objects it must include identifiers such as pzInsKey and pyID. The best practice is that the reusable detail view should be created in the target class/data object class, then referenced from the parent view.
So if your address details belong to a Customer data object, the preferred design is:
create a Customer Details or Customer Address view in that class,
expose the Customer row as a data reference/object,
then use link/additional details to open that object’s view.
However, if the table is sourced from non-queryable or plain embedded data, link behavior is more limited, you can add an icon/link column and trigger an event-action pattern, launch a local action / modal dialog and pass row values and then fetch additional data from a parameterized data page using the clicked CustomerID. This approach is often more flexible than trying to force “Display as Link to Object” when the table row is not a real object reference
Technically, you can display the additional details in the same View using the Form Refresh Settings since this is a single Page Data Reference property.
Configure the Form Refresh settings for CustomerDetails.Name
Triggers the DT whenever there is a name selection
True but show additional details, with another View defined on the Data Object’s class should work. You can create any view you like - it must be of type Partial for it to show in this list (as it’s a read only view).
@MarcCheong Thank you for the insight. The issue was that these system created partial views are not coming in the dropdown, which gave me an impression that something is not working. But, once I saved as an existing view, it appeared for selection.(Of-course it came into partial views) and now if I create a partial view directly, it is also coming in the list for selection.
Blueprint Import created?UX Tab Created?You said these were “system created”?
There are some views, which historically have required you to go into them and save them at least once, so that the right metadata is created on the view for them to show. The same could be said for App Studio / UX Tab created new views, the metadata might not be finalised until you actually open it and save it. It could be that.
Relevant record caching - Even in '25 there are a few instances where newly created records/instances are not updated post caching - perhaps your testing cleared that cache. (less likely but still could result in this)
Without more testing, hard to say. If you get to the bottom of it, let us know!
Hi @VVNagaSaiN
Thanks for the approach. I have done the same steps that you have said
Now I can able to see my View in the dropdown.
I have given my view on the Channel Column
But when I am doing the same for the status column, it is not happening in this way
Should we need to change any property configuration? i.e., I am unable to click on the status column
Glad my approach worked. But yeah, as @MarcCheong mentioned, you can simply create a new partial view in your case type which is easier.
For this, I think the default format of Work Status is being applied to show that value in colors. Change the format to Text and this should work as any other property.
Thanks for the response.
There is a new issue we have observed when we are giving sources as a Data page to that the source is an API, and for testing purposes, we have given an alternative source, which is RD
So when we are fetching data from the API, the ShowAdditionalDetails feature is not working
But when we are fetching data from a local source, we are able to see the expected result of ShowAdditional Details.
Currently, we are using 24.2.3. Has anyone faced this issue? If yes, can we have a workaround for this
