Question
PayPal
IN
Last activity: 14 Feb 2020 3:06 EST
Column not exposed error - Obj Operations with External Table
Hi,
I have created an external table in My SQL and created corresponding class and properties using external class db mapping wizard. However , I am not able to do any Obj- operations on the table as I am getting "columns not exposed error". but the columns are shown mapped to properties in the external class db mapping properly. can somebody help?
EXCEPTION: com.pega.pegarules.pub.database.ConfigurationException: Database-Config-KeyPropertyNotExposed
Pegasystems Inc.
IN
Hi Ashwin,
Are you able to populate the property values of this table when you run the case type?
Do you see the value of these columns in the clipboard?
Could you please attach the screen-shot of the class definition tab and external mapping tab.
Also the exception says that the key property is not exposed, so is the property mentioned as the key property in the Class definition tab exposed or not?
PayPal
IN
Yes..property values are populated and i could see them in clipboard on the corresponding page. But while trying to do the obj-save of that page to external table, property not exposed error occurs, however the key property mentioned in the class definition is exposed column in the table.
Pegasystems Inc.
IN
Hi Ashwin,
Can you check if the property name and column name are of same case(it is case sensitive), because if one is Capitalized and other is camel case we can expect this error.
If yes, can you alter the table column names as of property? Let me know if that helps...
Thanks.
Verizon
IN
Can you post the mapping details to see if you've configured the class key, column property naming correctly.
Also in case if you are not already aware, for any change you make to your external table, you should do a save of the Database Table data instance for the changes to reflect in Pega.
Updated: 14 Feb 2020 3:06 EST
Lanit Laboratoriya Novykh Informatsionnykh Tekhnologii
RU
I met the same error and solved it by rename column in database with a capital letters (so instead of ValueName column I create VALUENAME column)
If you have property ValueName (and if you even in external mapping use column in db as ValueName, see externalEx.png for example) pega will look for VALUENAME column in DB (but in DB you have only ValueName column), probably it's your case?