Getting SQL Report Resolver Error for Extenal Tables
Hi All,
We are getting Frequent Sql Report Resolver Error for some property for the External Tables, however the following property are been already present in the external tables.
We are using SQLServer 2017 and on PEGA 731 Instance at our end,
Error:
-
Like (0)
-

Hi There,
From there its clear that PRPC has encountered unexposed property in Report Definition.
In case property are already optimized could you reoptimize it.
Further can you check for the query that gets generated by RD. The query statement must not query the blob.
Regards,
Ujjwal

For External Tables PEGA does not support Property Optimisation from designer studio.
The following property is present in the external table, still getting the following error for all the external tables created.

Can you try running the following Java to verify if the column name is visible to the system
try {
String classColumns = tools.getDatabase().getColumnsForTable("PegaDATA","YOUR_TABLE").toString();
oLog.infoForced("classColumns: " + classColumns);
} catch (DatabaseException de) {
oLog.infoForced("We hit a database exception");
}
Also can you verify if there is a mapping between the column and property of the External Mappings tab of your Class rule.

When I run the Following
SQL Query : select pzPVStream from pegarules.pr4_base where pyDatabaseName = ? and pyTableName = ? is been used and if I pass the parameter nothing returns back, even I run the following on the SQL Client it doesn't return anything.

I'm not entirely sure why this would be useful in this instance.
Even if you supply the right database and table name, this is only going to return the Data-Admin-DB-Name rule information and the pzPVStream is binary and won't be readable.
If you want to verify if the column has been optimized, you might want to open the associated Property rule, then examine the XML for that rule. If it's optimized I believe it will list the classes that it is optimized for here (probably towards the bottom).

I have not created any external Property reference for mapping and thus the property name in Database and the property name in PEGA are same.
As per the error:
com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException .CentreName Unexposed properties cannot be selected for classes mapped to external tables.
Invalid reference getting for '.CentreName ' property.
Please send us the screen shot of external Mapping exist on the class on which above property created and column names should match with DB columns (consider it is case sensitive)

Did we find any solution for this issue. If so, can someone please share it.
If you are using external Table uncheck "Report on descendant class instances" from the Data Tab and save the report the following error will not come in the reports.
This is how it solve the issue at our end.