Difference between revisions of "Upgrading from opentaps 1.0 to opentaps 1.4"
From Opentaps Wiki
Jump to navigationJump to searchLeonTorres (talk | contribs) m |
|||
| Line 3: | Line 3: | ||
* If you have custom UI labels, they may be loaded by adding them to <tt>LabelConfiguration.properties</tt> in <tt>opentaps-common/config/</tt> | * If you have custom UI labels, they may be loaded by adding them to <tt>LabelConfiguration.properties</tt> in <tt>opentaps-common/config/</tt> | ||
** If previously you were using <tt>UtilMessage.registerLabelMap()</tt> to load custom labels, you may now remove all calls to this function as it is no longer needed. | ** If previously you were using <tt>UtilMessage.registerLabelMap()</tt> to load custom labels, you may now remove all calls to this function as it is no longer needed. | ||
| + | * Run the upgrade SQL script in hot-deploy/opentaps-common/scripts/sql for the following: | ||
| + | ** <tt>ProductAverageCost</tt> has been re-factored to use a single productAverageCostId as its primary key. The script will alter the table and automatically fill in | ||
Revision as of 23:57, 30 March 2009
- Run the service opentaps.setSupplementalDataForAllParties to populate primary contact data for all parties.
- Configuration of GL accounts for invoice writeoffs have been changed. Instead of using GlAccountTypeDefault, they are now configured with InvoiceAdjustmentGlAccount with the adjustment type "WRITEOFF"
- If you have custom UI labels, they may be loaded by adding them to LabelConfiguration.properties in opentaps-common/config/
- If previously you were using UtilMessage.registerLabelMap() to load custom labels, you may now remove all calls to this function as it is no longer needed.
- Run the upgrade SQL script in hot-deploy/opentaps-common/scripts/sql for the following:
- ProductAverageCost has been re-factored to use a single productAverageCostId as its primary key. The script will alter the table and automatically fill in
