Conversation

EY
US
Last activity: 4 Aug 2025 9:39 EDT
Best Practices for Overriding OOTB SDK Components and Troubleshooting
I have two questions that I was hoping to get answered here regarding overriding SDK components that pega provides in the event that you want to extend the functionality that have for some of the OOTB components provided.
1. I was trying to override the field component for "Field Group". I wanted to add two additional parameters to App Studio, so that the collapsed sections can be collapsed by default and so that the heading for the field group can use a property reference instead of a constant header. I was able to successfully override it and add the additional parameters to the config-ext.json. However, when I attempt to publish the component to my dev environment I am getting the following error - "No config-ext to publish for Group" and the overridden component is not showing in my dev environment. Please see attachment.
2. I noticed that not all components that can be overridden have a config-ext.json file to it. For these components is the expectation is that you should not add additional parameters to the component to be available on App Studio? It was also requested to be able to make the records in a repeating view be collapsible. I was trying to add another parameter to FieldGroupTemplate.tsx, but it does not have a config-ext.json and it is unclear what is the subtype should be set to for the that file if I have to add that manually. Just wondering what is consider best practices when you do need to override these components.