Question
Navy Federal Credit Union
US
Last activity: 12 Feb 2024 13:54 EST
Using report definition rule with muliple class joins in data flow rule
Hi, has anyone faced this issue? If yes, were you able to resolve it?
Report definition rule allows you to join multiple tables with association/join/subreport. Primary class/table data are available in pxResults page and joined class/table data are available in an embedded page of pxPages(). We would like to use this report definition as the source data in a data flow rule. In data flow rule, we are not able to get the data of embedded pages in any of the shapes, such as data transform rule shapes in the data flow rule.
Looking forward to your input/suggestions/solutions. Thanks in advance!
Accepted Solution
Updated: 13 Feb 2024 5:55 EST
Pegasystems Inc.
GB
@AhmedAttia @VenkatA2871 I can see that a support issue was logged last year:
INC-A1995 (Using report definition with muliple class joins in data flow)
It was closed with the following details:
As discussed, the support for report definition is only partial when used within context of report definition.
The use case you are referring to in your requirement is not supported in the report definition when its used as a primary dataset in the data flow. You need to use compose shape to join instead of using join condition within report definition.
Pegasystems Inc.
GB
@VenkatA2871 In a data flow rule, you can use a Data Transform shape to access the embedded pages data from the report definition. In the Data Transform rule, you can reference the embedded properties using the appropriate syntax, such as .pxResults().pxPages(W).PropertyName, where W is the prefix used for the subreport join in the source Report Definition. Make sure to configure the Pages & Classes tab in the Data Transform rule to include the correct class for the embedded page.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy:
Populating a data page by using a report definition
Knowledge Expert
FR
@VenkatA2871 hey Venkat, any updates on this ? i am facing the same issue.
Thank you !
Accepted Solution
Updated: 13 Feb 2024 5:55 EST
Pegasystems Inc.
GB
@AhmedAttia @VenkatA2871 I can see that a support issue was logged last year:
INC-A1995 (Using report definition with muliple class joins in data flow)
It was closed with the following details:
As discussed, the support for report definition is only partial when used within context of report definition.
The use case you are referring to in your requirement is not supported in the report definition when its used as a primary dataset in the data flow. You need to use compose shape to join instead of using join condition within report definition.
Pegasystems Inc.
US
@AhmedAttia @VenkatA2871 Data Flows have few limitaion pelase configure the use case by reviewing them