PRB: Printing reports modified for Zetadocs fails with error " The selected entry could not be processed due to insufficient customer information"
Print
ZTN4247
ID: ZTN4247
This Zetadocs technical note applies to:
- Versions 5.0 – 5.5 of Zetadocs for Microsoft Dynamics NAV
Symptom
When printing a NAV report to Zetadocs that is not based on standard sales or purchase tables, the following error message is shown:
" The selected entry could not be processed due to insufficient customer information"
The printing then fails so the documents cannot be sent with Zetadocs.
Cause
This error occurs because the Zetadocs send mechanism needs some metadata about the record in order to calculate what the archive sub folders should be. Unfortunately there is an error in the Zetadocs code which means we are attempting to calculate the location of these sub folders even if archiving is disabled.
This works correctly with the standard sales and purchase tables because the information required for these tables is included in our standard configuration data.
Resolution
In order to correct this problem, information needs to be added to the Zetadocs configuration tables to provide details on how to get the name of the company related to the record being printed. If there is no company related to the record, fixed values can be entered.
To do this please follow the steps below:
- From Object Designer run table 9041212 – Zetadocs Metadata Mappings
- Add the following two records to the table, replacing the < Table ID> values with the correct ID for the table that your report is based on and < Field ID> with the field in that table that contains the name of the company related to that record. If the record is not related to a company, enter 0 and put “Other” in the Fixed Value field:
|
Table ID
|
Metadata Field Name
|
Mapping Type
|
Metadata Field Type
|
Table Field ID
|
Fixed Value
|
|
< Table ID>
|
ZetadocsDocumentType
|
FIXED
|
Text
|
0
|
Other
|
|
< Table ID>
|
ZetadocsOrganization
|
FIELD
|
Text
|
< Field ID>
|
- To test that this change has corrected the problem, simply run the report through again and it should complete without errors.
Status
This has been identified by Equisys as a problem with the software versions given above.
Last updated: 13th May 2013 (JW/MW)