@MichaelC16831869

When you use Edit Columns on a Data Type’s Records tab and add an existing property, Pega only changes which fields are shown in that grid. It does not create any new column in the database; schema changes happen only through Optimize for reporting or explicit database tools. It does not alter your application’s Report Definition; the Records tab uses an internal data source and your edit just affects the display list. It does not unlock or save anything into your rulesets. In most versions this is saved as a lightweight UI preference for that landing page, scoped to the data type and often to the operator or application, not as a runtime rule change. Your underlying data model remains the same whether the property is exposed or only in the BLOB. If you actually need that property for reporting or end-user lists, expose or optimize the property and then update or create a proper Report Definition or view. Think of Edit Columns as a designer convenience for the Records grid, not a data model or rule change.