Posted: 14 Dec 2017 2:19 EST Last activity: 14 Dec 2017 13:28 EST
Reporting on unresolved OnBoarding Cases - Referencing Other classes
I am working on the exercise 'Reporting on unresolved OnBoarding Cases' . On Page 250 of the System_Architect_Essentials_72_Exercise_Guide_032117 it asks to populate the Report with .Employee.Manager, .pyID, .Office, .Employee.StartDate, and .pxCurrentStageLabel .
I am creating the Report Definition in the TGB-HRApps-Data-Seating instead of the TGB-HRApps-Work-Onboarding as described in the guide. I chose to do this to see if I can reference the properties of the TGB-HRApps-Work-Onboarding class using a steppage pyWorkPage in a Report in a different class just as I do in an Activity. When I do it this way, the Report will not compile even though I refence it using pyWorkPage.
How can I reference properties on the OnBoarding class (or for that matter any other class) in a Report Definition? Do I HAVE to use a join? Is using a StepPage in a Report Definition not the same as using a step page in an Activity?
When creating reports you want to make sure that you save the Report to the class that contains the majority of the data. Remember that the classes are mapped to the tables in the DB, so when you saved the report to the Data class you were reporting on data from the table mapped to TGB-HRApps-Data-Seating.
In order to report on two or more different tables you will need to use a Class Join or an Association. In either case you can create INNER or OUTER joins to get the data you need for your report.