PRB: Unable to print to the Zetadocs Client from the Receivables Transaction Entry window when the Batch ID field is blank
This Zetafax technical note applies to:
In Microsoft Dynamics GP, when using the “Receivables Transaction Entry” window to create a new transaction, you experience an error when trying to print to the Zetadocs Client by clicking the button labelled “Print”. The error message box contains the message “EmbeddedCommandData object not created”. The Zetadocs Client does not launch.
The transaction does not yet exist in the GP database. Zetadocs for GP requires that the transaction be saved or posted before printing to the Zetadocs Client. This will most likely happen when the Batch ID field has been left blank and the transaction has not yet been posted.
There are 2 options:
- Assign this transaction to a batch (i.e. by ensuring the “Batch ID” field is filled in) and click “Save” to save the transaction, then lookup the transaction and click the button labelled “Print” to print to the Zetadocs Client, or:
- If you are not assigning this transaction to a Batch (i.e. by leaving the “Batch ID” field blank), you must first post the transaction before printing. After the transaction is posted, it is no longer accessible via the “Receivables Transaction Entry” window. You can access the transaction via the “Receivables Transaction Inquiry” windows. (E.g. by clicking the “Document Number” link to launch the “Receivables Transaction Inquiry Zoom” window then by clicking the button labelled “Print” to print the document to the Zetadocs Client)
After you have successfully printed another transaction to the Zetadocs Client, the original failed report will still exist in the Document Explorer in the Zetadocs Client. To remove this document, right-click on it, and select “Delete Document”.
This has been identified by Equisys as a problem with the software versions given above.
Last updated: 23rd February 2009 (PF/PS/MW)