I have noticed that when I add custom columns to SQL Server (I know not officially supported, but it’s for testing purposes), that when an Acumatica upgrade is done, these custom columns are dropped. It’s not a huge deal (that’s why we do RDS SQL Server backups before upgrade), but it seems a little counterintuitive that a drop operation is run on a column that the system doesn’t know about. This is probably the result of a complete table drop and refresh as part of the upgrade process.
Does anyone have any strategies for seamlessly moving over custom columns when an upgrade is run? I like the ability to manage the table structure at the SQL Server level, so if there is some way to do that which also plays nice with the Acumatica framework, that would be the best of both worlds...