Protected: Liaison EDD Client steps

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD DITs

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD Recipient Lists

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD Script routing options

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD Scripts overview

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD System Configuration

This content is password protected. To view it please enter your password below:

Protected: Liaison EDD Server installation

This content is password protected. To view it please enter your password below:

“Unable to Print” error from Liaison EDD Primary printer after Windows 10 upgrade/update

The recent Window 10 Anniversary update has caused printer connections to be lost.

ISSUE:  After an update to Windows 10 an “Unable to Print” message is returned when printing to the Liaison Messenger EDD Primary printer.

SOLUTION: Delete and reinstall the printers then re-register.

STEPS: Delete both Amyuni Document Converter and Liaison Messenger EDD Primary from Devices and Printers.   Right click > Remove Device.

Using File Explorer go to the shared LiaisonEDD folder
Double click AMYINST.EXE.  Click OK when complete.
Next run the License Manager from LIALICMGR.EXE in the LiaisonEDD folder
Click Register then click OK once the printer is added.
Close the License Manager.

Once refreshed print a test page from Printer Properties and verify the PDF is created in LiaisonEDD\Queue1

NOTE:  The Amyuni Document Converter and Liaison Messenger EDD Primary are grouped under one icon in Devices an Printers.  Right click the one that appears and choose Printer Properties to see both.

Adding Liaison EDD Data Identifier Tokens (DITs) to Crystal Reports

The Data Identifier Tokens are the key link between the report output and the Liaison EDD processing scripts.    There are two methods for creating these DITs within a Crystal Report.  This article provides step by steps instructions covering both methods.

The first task is to define which data fields will be linked.   The DIT Values tab of the script is used to enter these fields.  In most cases the standard values will be pre-populated. You do not need to enter the specific field name in this section as it is not read during processing.  Use a name descriptive enough to identify the field.  The specific data field can be inserted in the formula field in Crystal after the DIT has been added.
After entering the values on the various tabs click “Save DIT Values” on the right.
CR_DIT_1

Click the Report Master File tab and select Crystal Reports from the Report Writer/Source Document list.  Use the yellow icon to the right of the File Linked to Script field to select the report file used with this script.  The Base File Name field will reflect the file name of the report selected.
CR_DIT_2

Click the Generated DITs button next.   Click Yes when prompted to Generate DITs?
CR_DIT_3

With Crystal Reports installed on the machine where Liaison EDD Server is running you will then be prompted to have EDD attempt to insert the DITs into the Crystal Report automatically.   Click Yes to perform this action.
CR_DIT_4

If the Crystal Report Runtime or API report license are not valid the DITs are not added.  A window will appear indicating the attempt failed and the DITs will need to be added manually.  Refer to option 2 at the end of this post for the steps on adding the DITs manually.
A window will tell you the tokens were successfully generated. Click OK.

At this point a backup of the original .rpt file is saved in the BACKRPT folder of the main LiaisonEDD location.  The path is listed in the Last Backed-Up File field at the bottom of the screen.   The original file can be restored by clicking Restore Last Backed-Up File on the right.
CR_DIT_6

The next steps is to review each formula field.  Use the Call Report/Source Editor… button to launch the report in Crystal.   You will be prompted to create another backup of the field.   Only click Yes if changes have been made directly within the Crystal Reports since the last backup file was created.
CR_DIT_7

When the report opens you will see the DITs listed under the Formula Fields section of the Field Explorer.  In most cases the names begin with _EDD and appear at the top of the list.   Each field is added in the Page Header section.   The fields are layered in the upper left corner with the font size set to 2 with a white font color.
IMPORTANT NOTE:   In most cases the printable area of the PDF is smaller than a regular printed copy.  Therefore, depending on the margins of the report, these fields may need to be moved into the printable area.  This may only need to be a few positions down and right.  Or they can be moved to any location in the same section.   The white font color keeps them from being visible on the page but can still be read by EDD.  They can also be placed behind any other fields within the page header if space is tight. For best results do not have more than one DIT exactly on the same line.  They are staggered by default when added automatically.

CR_DIT_8

Review each field in the Formula Editor to confirm that the expression is valid.
In this example “CustNo” was used in the DIT Values tab to indicate the customer number field is to be used in this token.
CR_DIT_9

In the expression replace the data field place holder {CustNo} with the actual report field reference.
Use the Check button (x-2) to validate the expression.   The ‘No errors found’ window will appear for a successful expression.
CR_DIT_10

Option 2

If the DITs are not able to be added automatically in the Crystal Report you can see the formula field expressions by clicking the View Generated DITs button on the Report Master File tab.  This opens a tokens screen.
The top portion of the tokens screen has instructions for adding the fields.  This includes the font size, color, field length and positioning.  The bottom portion has the individual expressions with the section they are to be placed.  The expressions are in Crystal syntax which allows then to be copied and pasted into the Formula Editor.   Note the ALIAS and DOCTP tokens are static text. They can be added as text or a constant in a formula field.  We find the formula field method allows them to be seen easier when editing the report due to the white font color.
Once the concatenated expressions are added replace any data field place holders with the report field and validate the expression as described earlier in this article.
CR_DIT_11

Click here for more information on emailing statements, invoices and many others from Dynamics AX 2012, Dynamics GP, Dynamics SL, Key2Act and Sage.

Dynamics GP – Liaison EDD incorrectly routing documents to printer after GP upgrade

We have noticed an issue where the GP Report Writer calculated fields used for Liaison EDD are being affected during an upgrade of Dynamics GP.   The result is the document being routed to the default printer selected in System Configuration.

If you experience this issue review the calculated fields in the GP report.
The following calculated fields are the ones commonly affected but we suggest you double check each one used by EDD.

_EDDalias
_EDDdoctp
_EDDalslr

Affected expressions will show double quotes in place of the constant. (example below)
This will be the entire expression for _EDDalias and _EDDdoctp.   Only the first constant in _EDDalslr is affected.

The expressions for each field can be found in Liaison EDD Server under Rules & Resources | Report Master File tab (per script) | View Generated DITs button.

GP_blank_DITafter upgrade

GP_blank_ALSLR_DITafter upgrade

Please contact support@liaisonsc.com with any questions or for assistance.