Best approach when DB sync table schema change issue

(0) Share

Report

Posted on by Ken Manhattan

396

Hello everyone,

I have a table with a field having type Enum, and after using for several time in production, we have to change the type to string, and result Build error, because of this conversion

May I know the best way to solve the error ? the error suggest us to delete the object (table), but it already contain many rows, also several object like data entity, security keys, forms that using this table. Wouldn't it produce more error if I delete the table ?

Can I get advice how to resolve this ?

Thanks

Categories:

Finance

All responses (1)

Answers (0)

Jonas "Jones" Melgaard 1,759 on at

Like (0)

Report

Best approach when DB sync table schema change issue

There is no fix for the error other than to rethink how to change the type of the field. And when you are in PROD, your options are pretty limited.

I'm used to creating a new field on the table, instead of changing the type; not removing the table. This approach leads to fewer issues but requires some effort in updating it in tables, etc. Once you have migrated the data using a job and are confident in the migration, you can remove the old field from PROD.

Can you use this approach?
Also, you mention security keys. Is this part of an ISV solution?