Field Mapping problems moving development to production
My development database has a series of upgrades I want to migrate into production. One of the updates has added 3 fields to a table, call them F1, F2 and F3. These are all global fields. There are script and layout changes to incorporate these fields and all are working fine in development. The setup has the user code in database U1 and the data is database D1.
When I add the fields to the production database (D1) and point the user code (U1) to use this database, the fields F1, F2 and F3 get jumbled. F3 - appears as <field missing> on the layouts, and F1 and F2 are reversed in their initialization script. If I switch the U1 to point back to the Development version of D1 - everything is fine again.
The development version of D1 was a copy of the production version 4 weeks ago. It is almost as though the creation order of the fields is what is being used, rather than the names.... any ideas who to get these upgrades installed successfully?