The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Implementing changes
Posted: 05 May 06 10:56 AM
|
melatonin and pregnancy in the human melatonin and pregnancy fiogf49gjkf0d I am new to SalesLogix. I am a contract developer for this company. I have made several changes to VBScrips, added a group, created new scripts. I have done this in a development database.
What is the best way to move these changes from the dev/test databases to production?
jc |
|
|
|
Re: Implementing changes
Posted: 05 May 06 11:06 AM
|
fiogf49gjkf0d Create a bundle, add all items to the bundle and then install the bundle on the production database using the Administrator. |
|
|
|
Re: Implementing changes
Posted: 06 May 06 1:29 AM
|
fiogf49gjkf0d Stephen's book "SLXDeveloper" is a great resource (referenced on the home page of this site) or going to the Develpoment classes at SalesLogix are two great resources to help get you up to speed on how to do bundles and deployment and some of the other tips and tricks you need to know when developing in the SalesLogix environment.
Ted |
|
|
|
Re: Implementing changes
Posted: 06 May 06 1:31 AM
|
tylenol pregnancy dose tylenol pregnancy safety first trimester skydtsgaard.dk fiogf49gjkf0d Forgive me Stephen - I should not post when I am this tired - I meant that your book title is DevLogix - slxdeveloper just happens to be this great website's name and my mind and fingers did not communicate well when I typed that last post.
Ted |
|
|
|
Re: Implementing changes
Posted: 07 May 06 1:58 AM
|
cost for abortion in wa cost for abortion in wa fiogf49gjkf0d Also if you learn by example fire up the Bundler with a SalesLogix bundle. Pick a small one though. There is a bit of garbled mess in the upgrade or service pack bundles for instance, since they have to accomodate all changes but something like the Advanced or new Marketing pack bundle is a good place to start.
Second always create new versions of plugins. It's a poor man's version control but you always want to do this when you're first getting the hang of things so you can clean out older versions only when you're sure of yourself. You CAN shoot yourself in the foot but it takes a bit of the right mojo to screw things up royally. The book is the cheapest knowledge you'll find, second only to peicing that knowledge together from this site (completely free) and others like it. Another good source of material is the stock code provided by SalesLogix. It's not always the cleanest or easy to maintain but you can use it to get an idea of what works. |
|
|
|
Re: Implementing changes
Posted: 23 May 06 2:44 AM
|
fiogf49gjkf0d Hi John,
we recommend employing a third, TEST, environment which is an exact copy of your live system. Depending on the frequency, type and data changes you may want to refresh the test environment with a copy of production periodically.
It adds a little extra work but may save you production nightmares!
You would bundle up your changes and then apply them to the TEST environment, if need be let users test the changes also, then apply them to production.
The benefit is that if you missed any plugins, settings, security, or data changes, you would spot those in test, plus you have one more trial run before applying to live, and you can continue developing while users are testing changes without interruptions, say a latest vb script change erroring out etc.
For smaller changes it may seem a little extra work, like for a group for example, but in the bigger scheme of things it is a recommended practice. I don't know of any customers that do not have a test environment.
Gregor Anton
www.antonsolutions.com |
|
|
|