Forgive me if I've asked this question before or if it's well-trod ground by this point, but what is the recommendation for a common scenario (for us, at least) wherein a contractor works with us to develop custom screens in our TEST database but ends up losing their work when a LIVE to TEST copy happens. Surely there's a way to keep that information saved that doesn't involve simply re-entering it by hand - especially since the contractor may charge additional money for the time it takes for them to put that code back. During rollover, we typically do LIVE to TEST copies every other day until it's all worked out. I know this may not be very efficient, but I'm working on that one, believe me.
Anyway, I hope someone can point me in the right direction, even if it's just giving me a proper keyword search for the issue.
Thanks in advance, Tessiturians.
This is a super typical question in my experience. We regularly have the conversation before Live to Test Copies. Do we have everything out of Test System? What can be moved to Live Fast, so we don't lose it and don't have to manually copy it back into Test?
If we come up with a good way to do this, I think this would help all.