nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

PDF corrupted

fabulon12

Hi ! 
 
Here is my problem : I use BIRT 3.7.2 and I have problem when I generate a report to a PDF output. 
 
It begins to generate and then stop to open my PDF reader with a message "PDF corrupted" <a class='bbc_url' href='http://www.birt-exchange.org/org/forum/public/style_emoticons/'>http://www.birt-exchange.org/org/forum/public/style_emoticons/</a><#EMO_DIR#>/confused.gif 
 
The report contains 500 pages and I suppose that the problem is a kind of lack of memory or something like that. 
 
Have you ever seen that problem before ? 
 
My first solution is to use the report engine (3.7.2) with a command line, it works, but the problem is that the data are not sorted correctly. 
 
If you have any idea... 
 
Thanks.

Find more posts tagged with

Comments

mwilliams

So, the actual message is "PDF corrupted"? I've never seen this before. When you run your report with the command line, it works, but is not sorted correctly? How are you sorting, in your report?

fabulon12

Well, I've tried to generate de report one more time, and today it works without the "corrupted PDF" message !!! I can't explain that behaviour...

Well, the sort problem is still here. My report structure is the following :

- a list component bound to a dataset which is sorted on the query with the ORDER BY clause like this ORDER BY field_1, field_2, field_3. And the "preview results" output works fine.

Then I've tried to add a sort instruction on the "Sorting" tab in order to force the sort. Now the question is do I do it right ??

I've tried :
- field_1 + field_2 + field_3
then
- field_1
- field_2
- field_3

But the result is the same.

CBR

Hi,

sorting a huge result set should always be done in the database because it's a **** lot faster then the sorting on element level (because this is done by Java after the data was retrieved from database).

If you do not specify a sorting on the element level it always uses the original order of that results in the dataset.

Exception:
The table or list contains groups. If that's the case all data is resorted using the grouping key as criteria, so the original sorting gets lost (there is no setting or way to avoid that in the OpenSource version).

fabulon12

You're right about the huge data to sort on the database side. In my case the main datasat have only 60 rows.

Well I've had a look around the group and add the sort I wished via:

- Edit Group > Sorting tab and add the 3 fields

And it works ! Now I have my report correctly sorted.

Thank you for "group list" tip. The designer is so rich that sometimes I lose myself between all the parameters.

Thank you.