Problems exporting "Work Log for P...

[Thierry Draper]

Hi,

Using the v3.3.1 rich client I'm trying to export individual work logs for team members to analyse the tasks they have worked on between two specific date ranges, but I'm having problems exporting the data for some members of the team.  After clicking "Finish", the progress bar loads to around 40% immediately, the client becomes unresponsive for a while (around a minute or two) and when it comes back I can fully interact with the pop-up again (including the Cancel option), but no export is ever produced… even after leaving it alone for an hour.

The problem appears with the same users each time, so it doesn't appear to be random, and the only link I can see between those exports that work and those that don't is that the team members who I am unable to export a work log for record their time against lots of overheads and against many more tasks.

Many thanks.

Thierry.

[Tim Shelley]

Hi Thierry,

I guess you are using File | Export | Custom Reports and selecting the Work log for Person (csv)?

In the Rich Client under Help you should be able to collect all the logs into one zip to send me. Could you send me the rich client logs to ts@openxprocess.com?

Regards,

Tim.

[Thierry Draper]

Hi Tim,

I sent the logs through to you as requested on Friday - have you had a chance to look at them yet?

Regards,

Thierry.

[Tim Shelley]

Hi Thierry,

Sorry, I should have replied sooner. I saw in the logs an out of memory error, so I've raised a new issue: https://sourceforge.net/tracker/?func=detail&aid=2977089&group_id=251380&atid=1126707 with a possible solution.

You could try and increase the heapsize etc… but I think you will hit the same issue again.

Regards,

Tim.

[Thierry Draper]

Thanks Tim,

I presume there's no other way of getting that information out then?

Thanks again for all your help,

Thierry.

[Andy Carmichael]

The OGNL reports (of which "Work log for Person" is a quite complex example) work by defining an OGNL operation which returns a string. The string is then written to a file. It's clear that operations like this can navigate over a large model and as here run out of memory before it gets the chance to write the file. A better mechanism would allow records to be written out one by one as suggested in Tim's enhancement request (https://sourceforge.net/tracker/?func=detail&aid=2977089&group_id=251380&atid=1126707).

One possible workround in the meantime is to create the reports for shorter time periods. The "Reporting Dates" for these log reports are accessible if you double-click on the project and select the tab at the bottom of the editor. If youy produce these monthly, rather than for the whole project after it's been running a while, I think it's less likely you'll run out of memory.

Let us know if this works with your data!

Thanks.

Andy

[Thierry Draper]

Hi Andy,

I was still having problems with the "Work Log for Person" export, but was able export the same information using the "Work Log for Project or Task" in a roundabout way by reducing the reporting hours, so thanks for the tip!

Regards,

Thierry.