Question
Scotiabank
CA
Last activity: 28 Nov 2024 16:31 EST
AppStudio creating database columns for all properties
Hello,
We have observed that when we create any new property from AppStudio, it always creates a database column for it. Is there any configuration to stop this default behavior? We don't want exposed database columns for all properties we create.
I saw that other teams also reported this issue 4 years ago.
https://support.pega.com/question/creating-any-new-property-appstudio
Do we have any solution for this?
Thanks, Sandeep
***Edited by Moderator Rupashree S. to add Capability tags***
Maantic Inc
IN
Yes App Studio does that. If you want to reuse any property present on the inheritance path, you need to goto the Data explorer in Dev Studio and add the columns from the Records tab in the data type.
Scotiabank
CA
@SohamM95 - My concern is different. I have noticed that whenever I add a new field from AppStudio inside a concrete class, Pega always creates a column in the table mapped to the class and updates the report definition 'DataTableEditorReport.' I don't want this behavior; I want to simply create a property without exposing any table columns.
Pegasystems Inc.
CA
This is intended by design. Any new **scalar** property added to the Case type from App Studio, will be optimized and marked as relevant by default and added to DataTableEditorReport report Definition rule.
Scotiabank
CA
@RameshSangili -- Thanks for confirming. This is weird. Pega should have provided some checkbox or options to not expose or create database columns automatically. This is not only for Case Types; it's impacting all concrete classes. For example, we are using the Pega Common Data Model (CDM). If I create an app-specific property inside the Entity class Common-LDM-Entity-Account from AppStudio, it automatically creates a database column in the table data.common_account, which I absolutely don't want. These are Pega-provided CDM tables, and altering these can cause issues during Pega version upgrades in the future.
Pegasystems Inc.
CA
Thanks for the details.
When you source data from Pega Platform by using auto-map, no additional steps are required because the new field is automatically mapped to the source database table.
When using a remote system of record to store your new field, add the new field to the mapping between the source and the Pega logical data model in the Data Page Data Transforms. For more information about mapping data with a system of record, see Integrating with a data source.