Field is not appearing in view even it is marked as relevant

General
1

Hi I have a pagelist property which i need to use it in view, i have marked it as relevant but still cant see the field in views to add, how should i debug this ?

2

Sometimes when marking as relevant record from dev studio, we may need to re-login to use it in the views.

3

tried relogin multiple times but still same issue!!

4

Are you able to view the field in data model of your case type or data type for which you marked it as relevant record?

5

This property is not directly referred to either CT class or datatype class, instead it is embedded property say **pyWorkPage.Page1.Page2.Page3.ListProperty1(1).Page4.ListProperty2(1)
**
i have marked everything as relevant, but in view i could able to see till Page4, but not ListProperty2

6

Then you should mark ListProperty2 as relevant record in class of Page 4. Are you able to see ListProperty2 in data model of Page4’s data object? (To view its data model even if it is not a data type, right click on class in App explorer and select open in Data Designer.)

7

Yes since i have marked ListProperty2 as relevant i can see in the data model of page4 class but still i can’t see that property in view to use.

8

Can you create a view in page4 class and see if you can add that property there itself and use that view while using in your case type.

9

Can you once verify the relevant records present in this class Data-Tag-RelevantRecord ?

11

Page4 class is an pega OOTB class.

12

No i cant see.

13

Data-Tag-RelevantRecord this is the system class where Pega physically stores instances of relevant records and your property isn’t showing up, it means the record was never successfully saved or committed into the database table mapping. When you click “Mark as Relevant” in the UI, Pega writes an instance to Data-Tag-RelevantRecord.

You can try checking in and try merging your property if you are working in branch. If not working, try unlocking the version of that property and try marking relevant record again and check.

14

Thanks for the response if that is the case, I also cannot see the properties in the class you mentioned which are relevant and can be still used in the views. The only issue is with this property.

15

I think we can create views for OOTB classes as well.

16

You can try the below scenarios:

  1. If a property is marked as a relevant record in Dev STudio, for the property to reflect in App studio, user needs to log off and login.
    → If the property is properly marked as a relevant record, it will show up in the Data model tab of the corresponding casetype/data type(based on the class).

  2. If the property that was marked as a relevent record is a OOTB property
    —> Property can be direcetly added to the view by selecting the Page/Pagelist property which has class definition of the OOTB class
    —> Property can be added in the view directly in the OOTB class and then this view can be added in the required view using the Page/Pagelist (If the Data type is not visible in the App Studio, add the class to the Application Definition(Cases & data → Data), then log off and login)