For example from the AR Invoice Entry program after loading a group and selectig an invoice, when user clicks on "Action->Invoice->Print Invoice, you can see in ata that those parameters have been added to the trace data.
I would like to add some more data and be able to read them in the code. Any idea how?
Thanks for the quick link. Very interesting stuff. However I am trying to basically mimmick what Epicor does. I am trying to add parameters under the tracepacket tag just like the highlighted section but using client code:
Most all data on a form should already be available in the trace. Especially “key” fields like the AR group id. There’s an option in the trace settings to include just changed or all parameters. Choosing to include all should include everything. It’ll just make really long entries as entire datasets - even the null fields - will be included.
I do have access to data myself on form level in the code. I am trying to pass data to a function within code (Action->print invoice). This function requires invoice number. And I am not able to add the invoice number wherever its supposed to be so that the print invoice would pick it up.
I have access to data in my dataset, I just need to pass it to a print window.
In AR Invoice Entry, when user goes to Action->Invoices->Print Invoice, Epicor send the invoice number to the print window. I want to do the exact same this in code. Pass the invoice number to print window (Mimmicking the Print Invoices)