Цитата:
Сообщение от
Ruff
Дело в том, что после установки СП4 обнаружился странный глюк в стандартных (даже не затронутых доработками) отчетах: если в отчета встречается многострочное поле (в смысле для которого DynamicHeight = Yes: например, наименование номенклатуры), и очередная строка целиком не помещается на странице (как раз из-за этого многострочного поля), то происходит следующее: все однострочные поля строки переходят на следующую страницу (то есть перед строкой вставляется разрыв), но многострочное поле перепрыгивает аж через одну страницу!
....
Было такое. Исправлено в SP5. Но я не тестировал еще.
#10430
Reports in Microsoft Axapta were incorrectly printed when data in a field did not fit into a printed page.
• Problem
Reports in Microsoft Axapta were incorrectly printed when data in a field did not fit into a printed page.
When processing a report, Microsoft Axapta checked whether a field to be printed had the Dynamic Height property set to 'TRUE'. In these cases, if the text of the last record on a page could not fit to a single page, the application split the text and moved part of it to a newly created page.
Then Microsoft Axapta checked whether a section itself could fit to a page. If it could not fit, a new page was created. Thus, when a section could not fit to a single page and had fields with the Dynamic Height property set to 'TRUE', Microsoft Axapta incorrectly moved part of the information in a report line to a new page and created one more new page.
As a result, the report had the first page of a report printed correctly. However, the second page only contained part of the record, which was continued on page three. Thus, only odd pages were printed correctly, while even pages were printed with only one line consisting of part of the information from a record.
• Steps to reproduce
Open the AOT.
Go to Data Dictionary\Tables\InventJournalTrans.
Right-click InventJournalTrans and select Auto-report.
Follow the defaults and print the report to screen.
These issues becomes apparent if InventJournalTrans has more than one page of number of records.
• Solution
The code fixing the problem implemented in Service Pack 3 has been improved in Service Pack 5.
After the fix, when a new page is created by the field-splitting handling procedure, an internal flag is set to prevent the creation of a new page in further processing.