Тема: purchase order
Показать сообщение отдельно
Старый 18.03.2008, 17:00   #5  
gl00mie is offline
gl00mie
Участник
MCBMSS
Most Valuable Professional
Лучший по профессии 2017
Лучший по профессии 2015
Лучший по профессии 2014
Лучший по профессии AXAWARD 2013
Лучший по профессии 2011
Лучший по профессии 2009
 
3,684 / 5788 (200) ++++++++++
Регистрация: 28.11.2005
Адрес: Москва
Записей в блоге: 3
Цитата:
Сообщение от newbie Посмотреть сообщение
i think its purchase order form, then inquiries and then print from there
Well, there are several documents you can print from there: purchase order, receipt list, packing slip, invoice (the number of documents can vary depending on the localized functionality). Do you have do modify all of them?
Цитата:
Сообщение от newbie Посмотреть сообщение
If it is a report how to hide fields if empty? where to change code?
First off you must find the report which design you'll have to modify. You can achieve this by setting a breakpoint in the \Classes\ClassFactory\reportRunClass() method, next to last line of code:
X++:
args.name(selectedReport);
Then print the report as usually and when a debugger pops up look at the selectedReport variable value - this will give you a name of a node in the \Reports AOT subtree. Then you'll probably have to set AutoDeclaration property to Yes for the report controls you want to hide and play with their visibility depending on the corresponding field values. This can be done, for instance, in the fetch() method before a corresponding section is executed. It's hard to say in detail as there can be lots of nuances in the report design. For instance, one report can be used both for sales and purchase orders and you'll have to keep this in mind during modifications.