Hello,
As part of a consortium and for training/demo purposes, I was wondering how I might build an organization from the ground up that could include season packages, performances, promos, campaigns, sources, memberships...the works. So that I'll always have easy access to a sample org when needed without having to bounce around in Test to our various orgs within the consortium.
We wouldn't want this to live in LIVE because of the work to maintain it and the fact that it's a fake org makes it seem odd. So preference is to have it live in TEST or DEV. But with that in mind, whenever a refresh were to occur, the information I built for the organization would be erased. So I'm wondering if anyone has built already a script that we could run whenever the refresh occurs to reinstate this information back into TEST or DEV?
Thanks,
I'm afraid it doesn't sound particularly tenable: scripting all of that data would be an immense task, and just trying to copy it out and maintain it elsewhere wouldn't work because you'd immediately have index conflicts when your Live instance, say, assigned appeal_no 476 to something and you tried to copy back in appeal_no 476 from your fake organization.
I don't think there's too much of an issue with having the fake organization in Live, but one thing you could do (and I've done something like this from time to time) is give it its own control group/security access that is unavailable in Live to everyone but admins, and then run a post Live->Test script in Test which grants access to that organization to the users you want to be able to test things with it.
You still have the problem now of user work done in Test being sporadically blown away, and having to build new seasons and other structures every year in Live, but I don't think there's much of a way around that.
We have done things similar to this in the past.