Exposed property Not available in reports
Hi Team,
There is a Property been exposed to made it available for reporting. when I am trying to add it to a report of its same class, it is throwing below error as It is not valid. (but it is present in the same class and column exposed in back end table), This issue happening only in production but worked in UAT.
Q: Can I please get to know what are the scenarios causing this issue and resolution available? Please let me know if would provide more information when required.
Version 6.3 SP1
-
Property Name:
This is not a valid property, or this is a property that cannot be used here.
and below is the error traced while saving the report after adding the field.
Thank You,
Mathan
Hi Team,
There is a Property been exposed to made it available for reporting. when I am trying to add it to a report of its same class, it is throwing below error as It is not valid. (but it is present in the same class and column exposed in back end table), This issue happening only in production but worked in UAT.
Q: Can I please get to know what are the scenarios causing this issue and resolution available? Please let me know if would provide more information when required.
Version 6.3 SP1
-
Property Name:
This is not a valid property, or this is a property that cannot be used here.
and below is the error traced while saving the report after adding the field.
Thank You,
Mathan
|
***Updated by moderator:Marissa. Removed user added Ask the Expert and #helpme tags. Apologies for confusion, shouldn't have been an end-user option***
|
Optus
AU
Hi Mathan,
Once the column is exposed, you need save the existing "Data-Admin-DB-Table" instace which is associated to the class.
In general if you expose property of a class in dev evn, the "Data-Admin-DB-Table" instace of the associated class should be included in the product rule when promoting to higher environments.
ASB Limited
NZ
Hi Satish,
I had tried this saving the DB table instance once as well but it was not working,
Now i tried porting the DB table instance from Lower env to production but still it has not helped the same error persist. do you recommend restarting of server once? Please advice.
BlueRose Technologies
SE
Hi Santosh,
Are you getting any exception in the logs. If yes, please provide the stack trace.
Sincerely,
Prudhvi
BlueRose Technologies
SE
Hi Santosh,
Please go through the below links and may helpful for your scenario.
https://collaborate.pega.com/discussion/not-able-create-data-table-value-list-column
Thanks,
Prudhvi
Pegasystems
IN
1) Please do a test connection on the class definition to see if there are any errors reported
2) Please check if adding an external mapping in the class for this property helps
3) Please share the screenshot for this class and its properties from the Application Explorer
4) Please share a screenshot of the report definition where this property is being used
ASB Limited
NZ
Hi Rajiv,
1) No errors reported
2) Has not helped
3) and 4) PLease refer the attached document for screen shots
Please let me know your further inputs
Thank you
Mathan
Pegasystems
IN
Hi Mathan,
I looked at the screenshots and I am little confused. The error in this thread says that TRACKINGNUMBER is not an exposed property but the screenshot shows that the report definition select properties doesn't refer to TRACKINGNUMBER anywhere. Are we looking at the right report here?
-Rajiv
ASB Limited
NZ
Team,
I had made the report functional by porting the lower env report in production and it started showing up data for this field with no issue,
But if i check out the same rule and save it, the same error comes up again.
Still could not find what causing this issue in production machine alone.
Kindly waiting for your valuable inputs on this
Thank you
Mathan