
The installation of ImageLink includes inserting several entries into the
Dynamics SL's "Screen" table within the "System" database.
The purpose of these entries is to register several new screens to Dynamics SL.
The "Custom2" table within the "System" database is also
updated. Entries to this table are made via the Customization Import
process. This is the installation step where ImageLink access buttons are
added to standard Dynamics SL screens.
ImageLink stores information regarding specific document images in the table
"xIMIndex" within the application database. This is not a
standard Dynamics SL table. "xIMIndex" is created as a step
within the ImageLink installation process.

ImageLink is VERY compatible with Dynamics SL.
 | No Dynamics SL application data is modified by ImageLink. |
 | New tables are add to the Dynamics SL databases in accordance with
Dynamics SL guidelines. |
 | Customizations of Dynamics SL screens are made using Dynamics SL's
Customization Manager in accordance to Dynamics SL guidelines. For this
reason, Dynamics SL's "Customization Manager" is a requirement
to run ImageLink. |
 | Programs that access Dynamics SL databases are developed using
Dynamics SL's VBTools. This gives them the same look and feel as the
standard Dynamics SL screens. |
 | The installation process is performed with InstallShield®.
Dynamics SL tools such as DBupdate and Customization Import are used to properly
build and populate tables. |
 | The installation process has no effect on other customizations. |

Yes. The ImageLink grid shows the documents associated with the
current order. It also identifies documents associated with the
inventory item within the currently selected Dynamics SL grid line.
Assume, for example: A current order number 000123 is being
entered and one document relating to this order has been scanned and one
of the line items is for product XXX-ABC.
Also assume: Using one of the inventory screens, such as
Inventory Items (10.250.00), a picture of XXX-ABC had been scanned and a
word document that describes the product had been dropped into the Drop
Zone.
If the grid line that contains the product XXX-ABC is selected and the Images
button is clicked, then the ImageLink grid will show three documents
available for display. The first two will be related to the product
ID; the third is the document that relates to order 000123. You can
tell that the first two documents relate to the item rather than the
order, since their respective "Ref Nbr" fields within the grid
are empty (reference numbers are for Dynamics SL transactions, not inventory
items).

Very little. ImageLink was developed with Dynamics SL's Tools for Visual
Basic. Consequently, there is a tremendous degree of compatibility between
ImageLink and the Dynamics SL environment.
Care should always be taken when installing new software and updates.
Current backups are required and users should be logged out of the
application. The only requirement for ImageLink is that your delta.mnu
module must be backed up so that the ImageLink entries can be re-entered after
a new delta.mnu has been installed by the Dynamics SL upgrade process.

The short answer is that the documents do NOT have to be scanned twice. Here is the long answer:
The Order Management screens supported by ImageLink are:
Sales Orders (40.100.00)
Shippers (40.110.00)
Manifest Entry (40.115.00)
Shipment Confirmation (40.117.00)
Of these, the Sales Order and Shipper screens contain the customer number. When a document is scanned or imported (via the Drop Zone) from these two screens, the customer number becomes one of ImageLink’s index items. For this reason, the user can go to the customer maintenance screen and will find the document.
Back to Top
