Report Definition missing property
This is my first time writing Report Definition.
I have an existing ListView that I am trying to convert into a Report Definition.
My List view has 'FirstName' Property (in Class A) as one of the columns. When I try to use the same property in my Report Definition (under same class A) under columns to include, this property does not even show as the list of available properties. When I forcibly include the property .FirstName, the Report Definition does not save/compile and gives the error - Property Name: This is not a valid property. -
My assumption is that the FirstName property is not a scalar property on the pc_work table that the ReportDefinition is mapping to. Surprising that the ListView was able to access it but not the more 'advanced' Report Definition. Is there a way for me to retrieve the FirstName property in the Report Definition without changing the DB? Any example would be a great help.
Pegasystems Inc.
IN
This error doesn't seems to be coming due to unexposed column. Can you check the exact property name (including case sensitiveness), since RD needs exact property name. So if not tried already, Can you specify .FirstName instead of .Firstname.
Let us know if this helps :)
Accenture
US
I have tried but I still get the same error. In the pc_work table the First and Last Names are not exposed properties and are not even visible as the list of options to choose from.
In the drop down box to select available properties, ONLY exposed properties on the pc_work table are showing up as properties I can include in the columns. Is this the behavior of Report Definition?
HOW can I access LastName and FirstName properties which I assume are in the blob?
Accenture
US
Also, I created a new property called Testprop in the same class as the ReportDefinition.
When I want to include this as as a property in the ListView, I can see it immediately as one the values in the drop down box.
This same property is not available for as the list of values for Report Definition.
Is this how it is supposed to work? Do I have to expose a property every time I need to use a property in Report Definition? (I am on Pega 6 Sp2).
Areteans Technology Solutions
AU
Hey Chakri,
I want to check 2 things.
1) Is the ruleset which contains the Report Definition has the ruleset in which the property is created as prerequisite?
2) Is the property and the Report definition belong to the same class?
Accenture
US
I am not sure what you mean by 'prerequisite'. Can you please elaborate?
The new property, Report Definition and the List View ALL belong to the SAME class and are present/created in the SAME ruleset.
Can I use ONLY exposed properties in Rule Definition?
Areteans Technology Solutions
AU
The best thing about Report Definition rule is that it allows you to report on properties that are not exposed. So that should not be a problem. Although you will get a performance warning when you try to save the Report definition rule with an unexposed property.
Can you also check if all the three rules, i.e., Proeperty, LV, RD are in the same ruleset and same ruleset version?
Accenture
US
All three rules are present in the same Class, Same Ruleset and Same Ruleset Version.
Thanks for clarifying that the Rule Definition will allow me to report on properties that are not exposed. As you can see from my attached pics, other than scalar and/or exposed properties on my pc_work DB table, no other properties are showing in the drop down list when I try to create a Report Definition. But it does not happen for ListView Rules. What could be the problem?
Areteans Technology Solutions
AU
Chakri, i would suggest you to trace the entire save event. If possible find out the exact code that is flagging the entire execution with a RunEx. My gut feeling is that it is caused by ValidatePropertyName validate rule if i am not wrong. Do let us know the result of the trace.
Accenture
US
This article on PDN says that it is possible to report on UnOptimized properties in Report Definition
https://docs-previous.pega.com/when-use-and-when-not-use-unoptimized-properties-reports
in Pega 6.2 SP2.
I am using Pega 6.1 SP2. Is there any way to report on UnOptimized properties in Pega 6.1 SP2?
FDIC
US
Chakri
The feature to refer un-optimized property in Report Definition i.e. direct BLOB access in Report Definition was introduced in Pega 62SP2. It is not available in Pega 61SP2.
Report Definitions with references to un-optimized BLOB properties generate SQL that calls user-defined functions (UDFs) that open and access property values directly from the BLOBs stored in the DBMS.
These UDFs are automatically installed in the DBMS when v6.2 SP2 is installed or a previous PRPC version is upgraded to v6.2 SP2. Also, poor performance is very likely if un-optimized properties are used as sorting or grouping columns in reports, or used in filter conditions, in reports on classes with more than a few hundred instances.
You should optimize the property to refer it in Report Definition in Pega 61SP2.