Issue when moving Exposed Property to another environment
Hi,
As part of one of the application Data pages, we created a report to feed it, this required exposing an embedded property ".RequestInformation.Category". Data page worked as expected in Dev environment (hosted on Pega Cloud). However, when we moved the product rule to Staging environment I noticed the exposed property was not optimized...
We created Product rule with class groups and DB tables (also affected Class instances), however the column category_1 which was created on Dev, does not get created in Staging. When we check the Modify Schema wizard, the number of columns in Staging (226) is different than in Dev (229).
I heard we can use prpcServiceUtils to expose columns, however I'm not sure how to use it in Pega Cloud.
I know there is a lot of exposed/optimized property questions already, and believe me I checked many of them, but still not sure how to resolve this...
Thanks for any help on this.
-Jose
Aflac
US
Blue Zone Consulting Partners
US
@SanthoshB6893 thanks.
When I import the product in Staging environment, I get message that the changes are already present in the database. I tried re-saving the Database tables instances, but newer changes (category_1 column) are not detected.
Updated: 8 Apr 2022 17:06 EDT
Aflac
US
@josenavaswas there any explicit column mapping added in the class rule form ? I expect it because its an embedded property. can you check and if yes, include the class instance in the RAP?
Updated: 13 Apr 2022 11:14 EDT
Blue Zone Consulting Partners
US
@SanthoshB6893 right, once I optimized the embedded property it got added to the class definition:
I also included Class in the Product rule:
However, it still went unnoticed when I imported the product...
Regards,
Aflac
US
@josenavas If you are on 8.1.2, may be this is applicable for you.
https://collaborate.pega.com/question/pega-812-rap-exportimport-missing-schema-changes
@josenavas First thing is to make sure the schema changes for new columns are part of the Product rule. From the screenshot above I see that you included DB table so I expect the schema changes to be present in the RAP file. If they are present, while importing on the Staging environment, System will prompt for schema changes. Is this noticed during import on Staging environment?