Are you saying that in 7.6.1.2 the auto layout is more problematic than it was in previous versions? Or just that even in 7.6.1.2 there's an issue when you utilize auto vs fixed layout? If something has gotten worse, I would definitely open a case as there hasn't been a significant version update to the version of BIRT for a while (though it's listed on our roadmap to update the BIRT platform
https://ibm-ai-apps.ideas.ibm.com/ideas/MASM-I-427). It's been a few years since I was heavily involved in report development but I don't believe I've ever switched to fix layout. I worked on some extremely long running reports (like the Asset rollup) but those problems weren't so much in the amount of data being received but the calculations being done for the report so my focus was always on the SQL & the database. The out of memory issues I saw related to reports tended to be long running QBRs where they didn't provide the appropriate filter during report creation. I've unfortunately never had to tweak a report from a memory perspective that was returning the proper dataset.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 10-20-2021 21:01
From: Jeff Kish
Subject: Birt
I notice that in Maximo 7.6.1.2, selecting auto-layout instead of Fixed-layout can cause heap exhaustion eg out of memory for large reports- but this is the only way I have been able to get single tab xlsx output/exports. Does anyone know how to figure out how to ameliorate this?
#EverythingMaximo
------------------------------
Jeff Kish
interloc solutions
------------------------------