Question
Atos Syntel
IN
Last activity: 4 Jul 2017 7:52 EDT
what do the numbers under Set to visible and Count in view table step of modify schema indicate ?
What do the numbers 24 and 1002 indicate in the below screenshot ?
Accepted Solution
Atos Syntel
IN
1. The reason for the Set to visible count mismatch is due to properties with same name existing in same class under different ruleset versions, If you search for properties with column inclusion dropdown set to either required or recommended in the inheritance path of Data-Admin-Operator-ID class you will find pxCreateOpName and pxInsName present in two different ruleset versions (PegaRULES and Pega Procom) under @baseclass, so the appropriate one is chosen and shown in the table, the other property gets ignored resulting in the count mismatch.
2. Same goes for Count's value, i think this is taken as a total count of properties in the class and it's inheritance path (ignoring the duplicates and ones with availability set to withdrawn, no and blocked )
Pegasystems Inc.
US
Hi Dilipan,
Please check the pdn link below:
https://community.pega.com/sites/default/files/help_v718/procomhelpmain.htm
'Set to be visible' - Single Value properties in the class that are marked as Required in the Column Inclusion field on the Advanced tab on the property form. Values in this field are advisory only; they do not affect database operation.
'Count' - all properties in the class.
Thanks,
Susan
Atos Syntel
IN
Thanks for the link Susan, still not clear on couple of things
1. Set to visible count shows 24, but when click it, it opens a table listing 22 properties, similar mismatch can be observed in other tables also.
2. Count's values is 1002, we don't have 1002 properties under Data-admin-operator-ID class, if you include the properties in it's inheritance path it will be more than 1002 as @baseclass itself has 1048 properties (select count(*) from pr4_rule_property where pyclassname = '@baseclass').
Accepted Solution
Atos Syntel
IN
1. The reason for the Set to visible count mismatch is due to properties with same name existing in same class under different ruleset versions, If you search for properties with column inclusion dropdown set to either required or recommended in the inheritance path of Data-Admin-Operator-ID class you will find pxCreateOpName and pxInsName present in two different ruleset versions (PegaRULES and Pega Procom) under @baseclass, so the appropriate one is chosen and shown in the table, the other property gets ignored resulting in the count mismatch.
2. Same goes for Count's value, i think this is taken as a total count of properties in the class and it's inheritance path (ignoring the duplicates and ones with availability set to withdrawn, no and blocked )