Same Name Data type created
Since I was wrong in design, I erased the class and reworked the data type of the same name, the following error occurred.
-------------------
Warning : We were unable to create columns to match the new properties added. This will cause performance problems when using this data type. Please click here to fix this.
-------------------
The data seems to be able to be registered normally.
How can I get rid of warning?
J.P. Morgan Services India PVT Ltd
IN
Hello,
The reason for this warning is, that there are un-optimized properties used in the report. In this case we show column creation warning. We loop through the properties in report and identify if they are exposed or not. If there are any unexposed properties, we show this warning.
I hope this answers your query.
Pegasystems Inc.
US
Generally, properties are stored in Blob(in pzpvStream column of the respective table). Those properties you can consider as unexposed properties. To know more you can go through the help document. Please refer to below article.
https://community.pega.com/sites/default/files/help_v721/procomhelpmain.htm
Hope this helps.
J.P. Morgan Services India PVT Ltd
IN
check the below info as well:
EY Advisary
JP
Thanks.
But,I have not reached a solution.
Is the following "Open report definition class, do test connection and save it." Written in the URL article?
There is no change even after connecting test and saving.
If there seems to be a mistake, please point out.
Pegasystems Inc.
IN
Hi,
Please check if the property are already there in the DB? Is the issue still happening when you are trying to add new propery/column nanes to the Data type?
Please check the Table (deleted and the new table ) in your DB ,which will help in understanding the picture clearly.
Pegasystems Inc.
IN
Hi,
In pega check from the Database class mapping that which table is getting created and in your DB you can check for that table in DB(e.g oracle DB).
See the attched screnshot for the same.