We are experiencing an issue when displaying data in a Constellation view:
When using a property that references a data page, if the data page returns an error, the data is not displayed in the view, but no error message is shown to indicate that an error occurred.
This issue does not happen when we display the data page directly in the view : the error is correctly displayed at the top of the case.
Is there a way to display the error when using a property sourced from a data page?
Thank you.
In the attachment the current behavior of using directly a data page, the behavior we want when using a Property referencing a data page
@Adrien.Buot hi, can you explain a little more about the configuration you have? Field and how it is used on View and data page config would help understanding the issue.
What it means to display data page directly on a View?
The field is quite simple : Property Contact from the common data model, calling the data page D_Contact, this data page is calling a REST external connector
This property is displayed in our interaction case, we display some data about the contact, in the “Details” tab, it’s a Partial view.
As you can see in my first screenshot, my first view references this property Contact, this view is of class Common-LDM-Entity-Contact and displays basic datas (first name/last name/etc…)
A data page displayed directly in the view is a request view (the last one in my first screenshot) of type query, (my second screenshot shows this view).
So, when D_Contact throws an error (404 for example) I don’t have any error displayed on top of my case, but if the data page I use in the third view throws a 404, I can see the error displayed. The expected behaviour would be that both data pages throws an error displayed to the client.
'25 introduced more visibility over errors but its not in the release notes nor have i found the documentation on it (or looked too hard).
EPIC-83088 DX API [Data] to provide meaningful error messages
The CDM on top of this add extra complexity. It will require a deeper look at your configuration and expert assistance on what the DX API is returning + what is pega Customer Service / Common Application return. I would suggest raising a support ticket on My Pega Support to get the the assistance you need.
