Represent PropertyList as a Report Column?
I was trying to explain the benefits of Pega's preference for using embedded types like PropertyList to form many-to-many relationships.
But this comes up short when a report is needed to easily show all of the associated accessgroups.
Yes, there's a way to include custom sections via custom sections in a tooltip. But we shouldn't have to do this. We should allow Report builders to do this intuitively.
Trying this in v7.1.7 below.
Is there some wasy way of supporting this that I'm missing?
Pegasystems
IN
A report definition generates SQL that can only get scalar values back. Since a value list is a one to many, you can choose to get only the first (or any other specific) entry back by giving .pyAccessGroupsAdditional(1) in the report definition and it would use the UDFs in the database to get just the first entry.
For page lists or page groups, you would have to create the declare index rule and then use that in the "data access” tab of the report definition.
I will pass on your feedback to product management so that they can decide on the best way to achieve this.
BNY Mellon
US
Thanks. Yes, I can see how a programmer can see the Report Definition as an elegant SQL generator (which it is, and generally a good one at that). But if Pega wants to get architects to be able to think beyond traditional RDBMS limitations, this is one place to do so.