Saving a view from FW class to implementation class not showing the revelent properties

General
,
1

I’m working on Pega Sales Automation Migration. We have the Create view at (PegaCRM-Entitiy-Account). I did saved this view to my implementation class (ORG-APP-Account) class.

Eventought we have properties defined as relevent records, we are not able to acccess it ? what is the solution here

image
image478×411 2.11 KB

2

I understand you’re experiencing issues accessing properties defined as relevant records after saving the Create view from PegaCRM-Entity-Account to your implementation class (ORG-APP-Account) during your Pega Sales Automation migration.

  1. Verify Property Inheritance: Properties that are defined as relevant records can be inherited. Ensure that your implementation class (ORG-APP-Account) properly inherits from the parent class where the relevant records are defined. You can verify this by checking the class hierarchy.

  2. Check Relevant Records Configuration: Navigate to Dev Studio and verify the relevant records configuration:

    • In the header of Dev Studio, click Configure > Application > Inventory > Relevant Records
    • Confirm that the properties you need are properly listed as relevant records
    • Ensure these configurations are available in your implementation layer

  3. Update ClassMetadata: After saving the view to your implementation class, you may need to update the ClassMetadata:

    • In App Studio, navigate to Data > Account to open the Data object
    • Click Save to refresh the metadata
    • This step ensures that the system recognizes all the properties and their configurations in your implementation class

  4. Review Data Model Relationships: The system generates relationships between entities through the definition of page and page-list properties that are marked as relevant records. You can view the data model to understand these relationships:

    • In App Studio’s navigation panel, click Data > View next to the Data model header
    • This visualization can help you identify any missing dependencies

  5. Verify View Configuration: When you saved the view to your implementation class, ensure that all field references and data references were properly updated to point to the correct properties in your implementation layer.

If the issue persists after checking these areas, you may need to recreate the relevant record definitions in your implementation layer or verify that the property rules themselves are accessible in your implementation class.

3

I have seen this issue in my project intermittently. This issue seems to go away once after my logoff and login. However, I can’t reproduce this issue consistently.