Author Topic: General Upgrade Path Question  (Read 2935 times)


  • Guest
General Upgrade Path Question
« on: December 18, 2006, 01:05:01 PM »
I am getting ready to do a massive purge of our Pivotal system.  I want to purge everything that we are not using and will not use.  However, I have been told by people here that this may interfer with upgrading the system.

What have been your experiences with upgrading a heavily customized system?   Do we need to leave all of the OOB forms, security groups, DLLs, etc in place?   

Are there any gotchas in what I want to do that I should be aware of? 

Offline Rus

  • Administrator
  • Hero Member
  • *****
  • Posts: 122
  • Karma: +0/-1
    • View Profile
Re: General Upgrade Path Question
« Reply #1 on: December 18, 2006, 01:13:51 PM »
You can do 2 sorts of upgrade:

* platform upgrade - you just install new software and convert your bm into new customization toolkit format. in this case the considerations you mentioned are irrelevant

* full upgrade - this is in fact merging your bm with a new out-of-the-box bm using the instructions in the upgrade guide. the more you customize the more you will probably need to merge manually during that upgrade. this kind of upgrade is required if you want to make use of the precustomized features coming with the new version.

If you delete business objects from your bm completely I don't see why it's going to make things complicated during the upgrade - it actually simplifies the merger.
One Stop Shop Pivotal CRM Support and Development Service

Offline pivotalnd

  • Sr. Member
  • ****
  • Posts: 55
  • Karma: +0/-0
  • Gender: Male
    • View Profile
Re: General Upgrade Path Question
« Reply #2 on: April 17, 2007, 01:04:25 PM »
the default recommendation in any case - ALWAYS retain the OOB tables/queries/BO/ASRL's/searches/ASR's. It is never advisable to delete the OOB elements as an upgrade would not be a smooth process and will not go through due to many dependencies on OOB elements.

Hope this helps.