We recently upgraded from xTuple Manufacturing edition 3.8.3 to 4.4.0. In addition to this, we are also using an older version of the Project Accounting add-on (1.1.0). After the upgrade, we have been having 2 issues with the Project Accounting add on. When we go to tie an invoice to a project number, we would get an error whenever we tried to post an invoice. This issue was corrected by upgrading the Project Accounting package (now on 1.3.2).
However, we still had one outstanding issue. Whenever we try to look at project activity (CRM -> Reports -> Order Activity by Project…), we pick our project and hit query, and then get the following SQL error in the error log:
Thu Jun 21 11:08:31 2018 ERROR: schema “te” does not exist
LINE 123: LEFT OUTER JOIN te.teprjtask ON (prjtask_id = teprjtask_pr…
^
QPSQL: Unable to create query
In our database, this “te” schema does not exist, just as the above error indicates. When I restored a copy of the quickstart 4.4.0 database from xtuple.org, to my surprise, I noticed that this “te” schema actually existed already in the quickstart db. I went back to the earliest database copy i could find (3.8.4) and restored it, and found the same to be true there as well. I noticed there were other existing schemas that we do not have as well, but for what we need right now, the “te” schema is the important one. In our test environment, i went ahead and created the “te” schema, as well as all of it’s tables, functions, and other associated objects. When i did this, the error was resolved and Project Accounting was working as expected. My questions now are:
-
Could there be a reason the “te” schema was not included with our xTuple install?
-
Is simply creating the te schema, as well as its associated db objects the ideal solution to solve this?
There has got to be a reason that we don’t have this schema already, and I was just wondering if anyone had any insight as to why this could be. Thank you in advance!
