Overwriting Code

We have 3 environments and a SANDBOX. Code tested successfully in QA and was imported into Production and broke workflow. To fix, we ported code from Prod to a SANDBOX, then to QA, then to Prod again. The technical staff took 25 hours for our OOB applications with minor customizations

Re: Overwriting Code

. Liabt Sent: Thursday, August 23, 2007 1:15 PM To: arslist@ARSLIST.ORG Subject: Overwriting Code ** We have 3 environments and a SANDBOX. Code tested successfully in QA and was imported into Production and broke workflow. To fix, we ported code from Prod to a SANDBOX, then to QA, then to Prod again

Re: Overwriting Code

You trusted Migrator to do all that? I'm a pretty religious man, but that is beyond the limits of my faith. Part of using Migrator is knowing what it can and cannot be trusted to do well. It's like driving an old car you've owned for a while - you know it's weaknesses and limits, and you learn

Re: Overwriting Code

:15 PM *To:* arslist@ARSLIST.ORG *Subject:* Overwriting Code ** We have 3 environments and a SANDBOX. Code tested successfully in QA and was imported into Production and broke workflow. To fix, we ported code from Prod to a SANDBOX, then to QA, then to Prod again. The technical staff

Re: Overwriting Code

We are using Migrator 7.  However is this normal for the code to be missing between migrations? Is there a way to ensure/validate that the code really got to the destination?  I have trusted the migration report – should I not trust the migration report? Is it normal for the migration to