The classes to be considered are PurchFormLetter and its sub classes like
PurchFormLetter_Invoice etc. Other classes of interest are PurchEditLinesForm
can be visisted if you want to modify the form PurchEditLine which helps in an
intermediate conversation with user to set some options, like printing options,
summary update, whether actual posting should be done or not etc. also tables
like PurchTable, PurchParmTable, PurchParmLine, PurchParmUpdate,
PurchPArmSubTable, are critical and key tables for posting. You may put a break
point in the main() of PurchFormLetter and start debug, from there. Here u can
see that depending on the Args object coming from the caller (PurchTable- form)
the document status- purchaseorder, invoice, packing slip etc is xtracted and
the correspong child classes for that particular document status is
instantiated and the related Update() is done.
so start from main() of PurchFormLetter......cheers,
Sailendran Rajan
pranam mukher <[EMAIL PROTECTED]> wrote:
Hi Friends
Myself Pradeep , i am trainee in DynamicsAX 4.0 , i want to debug the
Purchatable form and table as well but i am not understanding where to start
,mainly i am concentrating on Posting( Purchase order,Receipt List,packing
slip,Invoice)..i want to know which tables are hit and from which tables data
come, when i click Purchase order,Receipt List, packing slip,Invoice buttons of
Posting.
Please help me in this regard...from where should i start debugging...i have
started with init method of Purchtable form but i am not getting clear Idea...
thanks in advance...
---------------------------------
5, 50, 500, 5000. Store N number of mails in your inbox. Click here.
[Non-text portions of this message have been removed]
---------------------------------
Be a better Globetrotter. Get better travel answers from someone who knows.
Yahoo! Answers - Check it out.
[Non-text portions of this message have been removed]
