SQL table mappings not carried over during custom upgrade
During the reconciliation part of our upgrade we modified a number of SQL Table mappings (moved some fields from M1 to M2 table and vice versa). After building the custom upgrade package and then applying it, we realised that none of these table mapping changes carried over. We won't have time the night of the upgrde to make manualy changes to all the relevant dbdicts, so does anyone know of a way to get these table mapping to carry over with the upgrade, or an easy way to copy them over after the upgrade.
Re: SQL table mappings not carried over during custom upgrade
Not 100% sure - we ran into the same issue - but I've thought about since our upgrade.
Once you know what the new fields are, can you add them to the DB manually _before_ you run the custom upgrade package? For example, if you're using SQL server, script out the changes that you'll be making to the tables, and run those first, before you run the upgrade package. If the fields already exist in the database, I _think_ the dbdict will use the existing fields.
If you script them out beforehand, you won't have to make manual changes to the dbdict, because you can run the SQL statements against the database