From Pega 8.1.0, i see that "CustomerData" is chosen as the schema for the tables of all the data types. Tables created in such way do not have any px, py and pz properties which include pzInsKey, pxObjClass or even pzPvStream. This restricts the data type from holding value other than the exposed columns. Is this a product defect? How to overcome this issue?
Obviously this is by design, not a product defect. In 8.1's App Studio there is seamless integration between your Data Type and whatever System of Record is used for that Data Type. You would not fetch a BLOB column from a non-Pega SOR data source.
As we know Pega readily handles case embedded Pages and PagesList sourced to a Data Type using the Data Page reference or snapshot pattern.
Are you wanting to embed a PageList within a Data class not using a Data Page to capture the data? Recall that Savable Data Pages were added in Pega 7.4.
Or are you not wanting to expose every column in your Data class?
But what happened to the good old "Data type having a table with blob column" approach? Is there no way to configure that from now on? All the data types that we create will be associated only with fully exposed external tables? I don't think it should boil down to an extent of cloning tables at the DB level.