Question 5 Replies 257 Views × Close popover Avinash Haridasu (Avinash.Haridasu) Morgan Stanley Morgan Stanley IN View Profile Send Message Avinash.Haridasu Member since 2014 285 posts Morgan Stanley Posted: July 29, 2018 Last activity: August 2, 2018 Posted: 29 Jul 2018 1:55 EDT Last activity: 2 Aug 2018 9:17 EDT Closed How does saving as a property in subclass impact performance I usually find the below error message when we try to save as a property in parent class in subclass for various reasons: A property of this name already exists within the inheritance path. Consider removing duplicate property definitions as they can negatively impact system performance. ex: pxAssignedOperatorID How does property saving impact performance. ***Moderator Edit-Vidyaranjan: Updated Platform Capability*** System Administration × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years ago Posted: 29 Jul 2018 7:50 EDT × Close popover Raveendra Mothukuri (Raveendra) Incessant technologies pvt ltd Technical Lead Incessant technologies pvt ltd IN View Profile Send Message Raveendra Incessant technologies pvt ltd replied to Avinash.Haridasu Above message tells that you are un necessarily creating same property. If already property exist in inheritance path,creating a same property is useless. Posted: 2 years ago Posted: 29 Jul 2018 9:43 EDT × Close popover Gayatri Nistala (Gayatri) incessant incessant IN View Profile Send Message Gayatri incessant replied to Avinash.Haridasu Adding to raveendra, if you want same property in work class, you can create in work class and reuse the same wherever you want. Posted: 2 years ago Posted: 30 Jul 2018 4:42 EDT × Close popover Marc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. FR View Profile Send Message MarcLasserre_GCS PEGA replied to Avinash.Haridasu Yes absolutely, you should always avoid unnecessary rules creation. Mainly for better (easiest) maintenance of your application and in the end for best application performance. Posted: 2 years ago Posted: 1 Aug 2018 0:59 EDT × Close popover Avinash Haridasu (Avinash.Haridasu) Morgan Stanley Morgan Stanley IN View Profile Send Message Avinash.Haridasu Morgan Stanley replied to Avinash.Haridasu Thanks for the replies. I understand that we should avoid duplicating properties. But for example a property pxAssignedOperatorID, is saved in 5 classes with a slight change of reference (linked property). In such cases what impact does it have on the performance. I'm specifically trying to understand the performance impact. Posted: 2 years ago Posted: 2 Aug 2018 9:17 EDT × Close popover Marc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. FR View Profile Send Message MarcLasserre_GCS PEGA replied to Avinash.Haridasu hello, I believe (but it might not be the full explanation) this is just adding more rules to be checked by our rule resolution mechanism. So the more rules you having longer it will takes but I don't think we have any metrics about this.