Could you please check if the property names in your external class and column names in external table are same?

Also, Pega doesn't support MySQL database. I am not sure if support is there for external table or not.

But as per my knowledge, there is no module in database layer which can consturct SQL query for MySQL database.

Ravi is correct. Pega doesn't support MySQL database.

Can you check whether the test connectivity on MySQL database rule succeeds or not? If it fails I think you need to use the databases that are supported by Pega https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find

Property names are exactly (even the case) same in mapping tab. Test connectivity succeds in Database rule and it gives the message Successfully connected to database Inventory. Also, in Database Class Mappings landing page there is a cloum Rows, which gives acurate number of rows in corresponding MySQL table. Therefore, I guess there is some level inteegartion avaialbe for MySQL.

May be the SQL queries used for test connectivity and database class mappings LP worked in MySQL because they are same across all databases. But MySQL is not supported by Pega.

Please go through platform support guide-

https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find

You are right. There is no reference to MySQL in the Platform Support Guide. Thanks for the quick responses.

I have migrated our database from MySQL to MS SQL Server 2012. I don't see this issue anymore.

Thanks,

Mahesan