Hi Jean Pierre,

if you have a backup of database, then you could restore and start migration with admin user again. ProjeQtor recognizes, if you restored database is from a previous version and migrates automatically.
May this helps.

Best regards,

Klaus

Hi Jean Pierre,

Planning calculation starts by erasing existing planning in plannedWork table, so this is not an issue.
But planning should instantly fill it with new data. So it should not remain empty.

Could you check for errors in log file ?

Also, Klaus idea is a good one : restore data and test again.

Hi,
Thanks for the suggestions.
I've restored the last backup done before upgrading.
Then starting the migration has given an error on table "tempupdate" because it was already present, I think this was not an issue, so I've dropped this table from the db and done again the restore.
This time the migration went fine, and the planning reports were showing the planned work.
I've then relaunched the planning calculation and planned work is gone, the table is empty and no error has been shown nor recorded. Here follow the log of what I've done. I'll have a look at what has been changed in planning calculation between the 2 versions.

Ciao
Jean Pierre

2015-01-08 09:33:57 ===== TRACE =====
2015-01-08 09:33:57 ===== TRACE ===== =====================================
2015-01-08 09:33:57 ===== TRACE =====
2015-01-08 09:33:57 ===== TRACE ===== DataBase actual Version = V4.4.2
2015-01-08 09:33:57 ===== TRACE ===== ProjeQtOr actual Version = V4.5.3
2015-01-08 09:33:57 ===== TRACE =====
2015-01-08 09:33:57 ===== TRACE ===== =====================================
2015-01-08 09:33:57 ===== TRACE =====
2015-01-08 09:33:57 ===== TRACE ===== VERSION V4.5.0
2015-01-08 09:33:57 ===== TRACE =====
2015-01-08 09:33:57 ===== TRACE ===== 1 lines updated into table "accessprofile".
2015-01-08 09:33:57 ===== TRACE ===== 1 lines updated into table "accessprofile".
2015-01-08 09:33:57 ===== TRACE ===== 1 lines inserted into table "dependable".
2015-01-08 09:33:57 ===== TRACE ===== 2 lines updated into table "planningmode".
2015-01-08 09:33:57 ===== TRACE ===== 1 lines inserted into table "accessscope".
2015-01-08 09:33:58 ===== TRACE ===== Table "audit" altered.
2015-01-08 09:33:58 ===== TRACE ===== 11 lines deleted from table "columnselector".
2015-01-08 09:33:58 ===== TRACE ===== 0 lines updated into table "assignment".
2015-01-08 09:33:58 ===== TRACE ===== Table "assignment" altered.
2015-01-08 09:33:58 ===== TRACE ===== Table "planningelement" altered.
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== DATABASE UPDATED
2015-01-08 09:33:58 ===== TRACE ===== WITH NO ERROR
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== =====================================
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== VERSION V4.5.3
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== Table "tempupdate" created.
2015-01-08 09:33:58 ===== TRACE ===== 0 lines deleted from table "tempupdate".
2015-01-08 09:33:58 ===== TRACE ===== 0 lines inserted into table "tempupdate`
(SELECT".
2015-01-08 09:33:58 ===== TRACE ===== 0 lines deleted from table "tempupdate".
2015-01-08 09:33:58 ===== TRACE ===== 0 lines deleted from table "workelement".
2015-01-08 09:33:58 ===== TRACE ===== ACTION '' NOT EXPECTED FOR QUERY : DELETE FROM `tempupdate` WHERE 1=1;
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== DATABASE UPDATED
2015-01-08 09:33:58 ===== TRACE ===== WITH NO ERROR
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== =====================================
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== DATABASE UPDATE COMPLETED TO VERSION V4.5.3
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:33:58 ===== TRACE ===== =====================================
2015-01-08 09:33:58 ===== TRACE =====
2015-01-08 09:34:03 ===== TRACE ===== NEW CONNECTED USER 'jph'

Hi,

I've restored the previous version to check that the last changes done will not have broken something into the database, but adding the last imputations and running the planning again is done with success.
Can you precise me which are the source files involved in the planning calculation, I can try to find where the bug is.

Thanks in advance.
Ciao
Jean Pierre

Hi,

Planning calculation is done in /model/PlannedWork.php, method plan().

For me, it works fine with V4.5.3.
I suspect some access rights issue.
Could you first try to connect as admin or other user with all access to all projects and try again ?

I'm doing this as user that has admin privileges on all projects.
I'll keep in mind the access rights, because it's strange that there are no error messages issued.

Hi,

thanks for the remarks, I've found where was the problem, or at least part of it.

I have created "internal" projects for each of my clients so I can easily edit my invoices for each of them at the end of the month.
Then I have "time & materials" subprojects of these "internal" projects and I create activities inside these subprojects.
Until now I was declaring rates of affectation of resources only for the subprojects, while they were at 0% for my "internal" parent projects. Until now this was working fine, but for the last upgrade the calculation of planned work was providing a null result. Just giving a proper rate to affectation for the parent projects has solved the problem. Now planned work seems to be correctly calculated again.

Any suggestion to better understand such behaviour is welcome.
Ciao

Jean Pierre

Hi,

You put the finger on the correct origin of the issue.
In V4.5, the affectation rate determination has changed because it now takes into account start and end dates of affectations.

The fact is that % rate is a limitation that is controlled on sub-project and top-projects.
So, the applied affectation rate limit on each sub-project cannot be more that rate on top project.
So, having rate of 0% should have brought the issue on previous versions, but this was possibly a bug that new functionality fixed.

Planning calculation is done in /model/PlannedWork.php, method plan().
And it works fine.