Why would a data reference field I create change into query?
You Asked: A Constellation Series
Great questions deserve to be shared! In our daily roles within the Pega ecosystem, the leaders of the User Experience Expert Circle address a wide range of questions. “You Asked” is our new series where we share these anonymized questions and answers with the wider Pega community. Our goal is to foster a space for shared learning and to help everyone build their expertise in Pega Constellation, together.
In Pega, there are often many paths to a great solution. We invite you to share your own experiences and alternative approaches. Join the conversation below!
A great question I had to do, and an opportunity to share some insights with the community.
Infinity ‘25 introduced limited support for Abstract classes in Constellation but prior, abstract classes only supported query fields. The use of abstract class as the source for the data reference was causing the conversion to Query.
See also: Abstract classes in Constellation are not a best practice - Knowledge Share - Pega Forums
I had the same observation when the Property is defined as “Data Reference“, however it changes to Query.. Is this because the Property of the Data object is defined in Modular application instead of the Current application?
you can use a data reference from a lower layer (modular application). The source of the problem is if you build your classes manually, choosing to use Abstract Classes. Constellation is a change in architecture, Blueprint is a change in methodology - using both, via Blueprint Import or New Data wizard will always build Concrete Data objects. The question is if that object has records or not (which for the abstract use case, we would not have records).
In ‘25, there is limited support for Abstract Classes, but you will still encounter limitations. It’s not commonly known, so I posted recently about it.
2 Likes
