Table of Contents

Troubleshooting: Commit error after exposing new column


A developer asks:

I'm trying to use the memo field of History to hold a list of the names of properties that were updated.  The property .pyMemo is an exposed column of 255 characters but is not long enough, so we are going to use a new BLOB column. 

First, I created a clone of the property and deleted pyMemo.  Then I made all the necessary database table changes. But when I try to commit to the database, I get an error message indicating that pyMemo is an invalid column. 

Since nothing requires pyMemo, why this error message?


To clear this message after making such database changes, stop and restart the Process Commander server.

Pega Platform 7.1.1 - 8.3.1 System Architect System Administrator System Administration
Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.