- App Store
When you upgrade from one version of xTuple ERP to another, it is required that you upgrade the core xTuple software. For PostBooks users, this means the core PostBooks database must be upgraded. For commercial edition users, this means the core Standard Edition database must be upgraded. Performing an upgrade to the core software is a prerequisite for moving from one version of xTuple ERP to the next.
It is not always necessary, however, to upgrade the extension packages or other applications which operate with xTuple. That's where this compatibility matrix comes in. This matrix is designed to help ensure your extension packages and other applications are compatible with the xTuple ERP version you are currently running—or upgrading to. The following packages and applications are covered by this document:
- Manufacturing Package
- xTuple Connect
- Time and Expense
- Project Accounting
- Enhanced Commissions
- QuickStart Wizard
- Third-Party Apps
If you are a third-party application developer and would like to have your application information added to this compatibility matrix, we invite you to help us keep this matrix up-to-date.
The manufacturing package (xtmfg) is a commercial extension of xTuple Standard Edition. When added to a Standard Edition database, the manufacturing package upgrades the database to the Manufacturing Edition. During version upgrades, it is not always necessary to upgrade the manufacturing edition package.
xTuple Connect is a commercial application which operates with all xTuple ERP Editions. The xTuple Connect application consists of two parts: a GUI client and an extension package (xtbatch). The xTuple Connect GUI client version will always be the same as the xTuple Connect extension package version.
* Connect 3.6.1 cannot be installed for the first time on xTuple ERP 3.8.x. Upgrading your existing xTuple Connect to 3.6.1 is supported.
** Batch Manager 3.3 will work with xTuple ERP 3.4 for the PostBooks and Standard Editions.
xTuple ERP versions prior to 3.0 are not supported on PostgreSQL 8.3.x. Also, as of xTuple ERP 3.8.x, versions of PostgreSQL prior to 8.4.x are not supported. If you are running xTuple 2.3.2 or older, you should not be running on PostgreSQL 8.3 or newer.
ALSO NOTE: Users who load backup files (e.g., empty.backup, quickstart.backup, and demo.backup) should be advised that as of xTuple 3.2.2 those backup files are being dumped from a PostgreSQL 8.3 database. That means the backups must also be loaded on PostgreSQL 8.3 (or higher) to avoid backward incompatibility problems.
|xTuple version||PostgreSQL Version|
|4.0.x||8.4 - 9.1|
|3.8.x||8.4 - 9.1|
|3.7.x||8.3 - 8.4|
|3.4.x-3.6.x||8.2 - 8.4|
|3.3.x||8.2 - 8.3|
|3.0.x-3.2.x||8.1 - 8.3|
|2.x||8.1 - 8.2|
|1.x||7.6 - 8.1|
The Time and Expense package (xttelite) is a free extension package which operates with all xTuple ERP Editions.
The Project Accounting package (xtprjaccnt) is a commercial package which can be added to any edition of xTuple ERP.
The Enhanced Commissions package (xtcommission) is a commercial package which can be added to any edition of xTuple ERP.
The QuickStart Wizard package (xtsetup) is a commercial extension package which operates with all xTuple ERP Editions. For the QuickStart Wizard to work, you must have the Desktop package (xtdesktop) installed.
The Updater is a free application used for upgrading databases and loading extension packages. The Updater may be used with all xTuple ERP Editions.
The Desktop package (xtdesktop) is a free extension package which operates with all xTuple ERP Editions.
The following table includes a list of third-party applications and the xTuple ERP versions they are compatible with. You can download third-party applications from the xChange. Also look for additional information about the applications on the third-party documentation page.
|Executive Summary Dashboard||1.0||x||x||x|
Fixed Asset Management
The Fixed Asset Management packages are a series of packages available for all xTuple Editions. The following table indicates the xTuple and PostgreSQL database versions the packages have been tested on.
|Package||Package Version||xTuple Version||PostgreSQL Version|
|3.6.x||3.8.x||8.4||8.4 - 9.1|
|Fixed Asset Depreciation||1.0.x||X||X|
|Fixed Asset Maintenance||1.0.x||X||X|
Wed, 05/05/2010 - 10:02#1
.qm files included in compatibility matrix
I am using xTuple Postbooks Edition V.3.3.0. I have not updated to newer versions because in the translation portal the only .qm file available for spanish is for this older 3.3.0. It would be good to include the available translation files in this compatibility matrix.
Mon, 05/10/2010 - 14:03#2
The 3.5.0 .qm files are available on the translation portal now. We upgraded all the projects last week. Meanwhile, older .qm files are generally compatible with newer xTuple versions. But, to your point, using the .qm version to match your xTuple version is always a good idea.
Sun, 07/31/2011 - 12:47#3
I have purchased a Quickstart wizard for version 3.6 .. Will this wizard work for version 3.7.0 which i have just installed?
Wed, 11/30/2011 - 10:51#4
Does the Enterprise edition upgrade gz file include the upgrade of xtbatch/xtconnect, xtprjacct, xtdesktop, and te packages? I am preparing to upgrade from 3.6.0 to 3.7.0.
Wed, 11/30/2011 - 10:55#5
I've converted this question to a support ticket. Let's take up the conversation there.
Mon, 02/13/2012 - 12:02#6
xt desktop package
How about the xtdesktop? Will the latest 3.7.1 work with 3.7.x and 3.8.x of the xtcore?
Tue, 09/04/2012 - 14:20#7
Can't believe I have never discovered this post until now! Thank you!
Wed, 01/23/2013 - 12:57#8
Upgrading From xTuple 3.5.4 to xTuple 4.0
If we wanted to upgrade from xTuple 3.5.4 to xTuple 4.0, what would be the process? Here is what have right now.
xTuple 3.5.4 Clients running on PostgreSQL 8.4.15 Server
Would I need to update the PG server to 9.1? The DB Matrix says it should work, but when I try to run XT 4.0 client gui, it fails against pg 8.4. I am guessing it would need to be updated even though the above compat matrix says otherwise. Thank you very much!
Wed, 01/23/2013 - 13:13#9
I was also looking at using an update script to do the job, but there only seems to be script from the database immediately previous to the one in question (ie. 3.5.3 to 3.5.4) How would I update from one severl generations apart (3.5.4 - 4.0.0 or 4.0.1)? Would I have update one level at a time? That is a lot of work and a lot o chances for error it would seem.