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.
Ideally, the developer is using a one-step deploy that can be run at any time, and works the same way when aimed at the TEST system, or LIVE for deployments and updates. Frankly, this is not particularly easy to do (and custom report setup XML doesn't play nice with this), but I think it's worth developing the skills, and holding 3rd-party contractors to that standard.