AnsweredAssumed Answered

What's the best way to update previously-installed custom code?

Question asked by Phil Gibbs on Aug 16, 2017
Latest reply on Aug 17, 2017 by Shad Mickelberry

Let's say I have the following custom files:

  • file1.php
  • file2.php
  • file3.php

I create a custom package (with manifest) of these three files which I can upload to our on-demand Sugar via module loader. I'll call this


At a later date, I need to fix a bug with the work, which involves editing file1.php and creating a new file4.php. So now I have these files which I need to get installed:

  • file1.php
  • file4.php


How do I get these two files (one of which is updated and one is new) on our on-demand instance, without affecting existing functionality or losing any data?


I thought of these possibilities:

  1. Load file1.php and file4.php as their own custom package, so both and this new package are installed simultaneously. But doesn't this mean file1.php is loaded twice (one of which is outdated)?
  2. Uninstall and load all four file[1-4].php as a brand new package, so only one copy of each file is loaded into Sugar at any one time. This feels like it could be quite messy as time goes on though.
  3. Something else?


I hope this makes sense. Thanks in advance.