1) How are documents scanned and indexed?

Documents are indexed automatically as they are scanned or “dropped” into the ImageLink repository.

  • Documents are scanned from a workstation where Microsoft Dynamics SL is active.
  • When a document is scanned, the contents of the fields of the Microsoft Dynamics SL screen are used as index keys.
  • The automated indexing also applies to non-scanned documents that are dropped into ImageLink’s Drop Zone.
  • The index keys for a document are stored in the table “xIMIndex” within the Microsoft Dynamics SL application database.

Back To top

2) What Microsoft Dynamics SL database tables are modified by ImageLink?

The installation of ImageLink includes inserting several entries into the Microsoft Dynamics SL’s “Screen” table within the “System” database. The purpose of these entries is to register several new screens to Microsoft 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 Microsoft Dynamics SL screens.

ImageLink stores information regarding specific document images in the table “xIMIndex” within the application database . This is not a standard Microsoft Dynamics SL table. “xIMIndex” is created as a step within the ImageLink installation process.

Back To top

3) How compatible is ImageLink with Microsoft Dynamics SL?

ImageLink is VERY compatible with Microsoft Dynamics SL.

  • No Microsoft Dynamics SL 2015 application data is modified by ImageLink.
  • New tables are add to the Microsoft Dynamics SL databases in accordance with Microsoft Dynamics SL guidelines.
  • Customizations of Microsoft Dynamics SL screens are made using Microsoft Dynamics SL’s Customization Manager in accordance to Microsoft Dynamics SL guidelines. For this reason, Microsoft Dynamics SL’s “Customization Manager” is a requirement to run ImageLink.
  • Programs that access Microsoft Dynamics SL databases are developed using Microsoft Dynamics SL’s VBTools. This gives them the same look and feel as the standard Microsoft Dynamics SL screens.
  • The installation process is performed with InstallShield®. Microsoft 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.

Back To top

4) Which Microsoft Dynamics SL screens are enabled for use with ImageLink?

ImageLink’s “Images” button has been incorporated into the following Microsoft Dynamics SL screens.

Accounts Payable

  • Voucher and Adjustment Entry (03.010.00)
  • Quick Voucher and Pre-Payment Entry (03.020.00)
  • Voucher Entry – Distributed Liability (03.025.00)
  • Manual Check Entry (03.030.00)
  • Void Check Entry (03.040.00)
  • Vendor Inquiry (03.200.00)
  • Document Maintenance (03.250.00)
  • Vendor Maintenance (03.270.00)

Accounts Receivable

  • Invoice and Memo (08.010.00)
  • Payment Application (08.030.00)
  • Payment Entry (08.050.00)
  • Document Maintenance (08.250.00)
  • Customer Maintenance (08.260.00)

Cash Manager

  • Cash Account Transactions (20.010.00)
  • Cash Account Transfers (20.020.00)
  • Bank Reconciliation (20.210.00)

Flexible Billings

  • Invoice and Adjustment Maintenance (BI.BAM.00)

General Ledger

  • Journal Transactions (01.010.00)


  • Receipts (10.010.00)
  • Issues (10.200.00)
  • Inventory Item Lookup (10.210.00)
  • Inventory Items (10.250.00)


  • Company Setup (13.250.00)

Order Management

  • Sales Orders (40.100.00)
  • Shippers (40.110.00)
  • Manifest Entry (40.115.00)
  • Shipment Confirmation (40.117.00)

Purchase Orders

  • Receipt/Invoice Entry (04.010.00)
  • PO Receipts Inquiry (04.200.00)
  • Purchase Orders (04.250.00)

Payroll/Human Resources

  • Employee Maintenance (02.250.00)

Project Budgeting

  • Budget Revision Maintenance (BU.BRM.00)

Project Controller

  • Project Charge Entry (PA.CHG.00)
  • Employee and Resource Maintenance (PA.EMP.00)
  • Project Maintenance (PA.PRJ.00)
  • Commitment Detail Inquiry (PA.CMD.00)

Contract Management

  • Contract Maintenance (CN.CON.00)
  • Project Change Orders (CN.COP.00)
  • Subcontract Change Orders (CN.COS.00)
  • Subcontract Payment Review & Approval (CN.PRA.00)
  • Subcontract Payment Request (CN.SPR.00)
  • Submittal/Transmittal Entry (CN.STE.00)
  • Subcontract Maintenance (CN.SUB.00)
  • Subcontractor Vendor Maintenance (CN.SUV.00)

Time and Expense for Project

  • Travel & Expense Report Entry (TM.ENT.00)
  • Time Card Entry (TM.TCE.00)
  • Timecard with Rate/Amount Entry (TM.TEA.00)


  • Requisition Item Request (RQ.100.00)
  • Requisition (RQ.110.00)

Service Dispatch

  • Employee Maintenance (SD.007.00)
  • Service Call Entry (SD.200.00)
  • Invoice Entry (SD.202.00)
  • Service Call History (SD.301.00)

Equipment Maintenance

  • Equipment Entry (SE.001.00)
  • Manufacturer/Model maintenance (SE.006.00)

Field Service

  • Service Contract Entry (SN.001.00)
  • Service Contract History (SN.017.00)




Back To top

5) Within Order Management, can the user see documents pertaining to a line-item inventory ID?

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 Microsoft 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 Microsoft Dynamics SL transactions, not inventory items).

Back To top

6) What must be done when a service pack is applied to Microsoft Dynamics SL?

Very little. ImageLink was developed with Microsoft Dynamics SL’s Tools for Visual Basic. Consequently, there is a tremendous degree of compatibility between ImageLink and the Microsoft 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 Microsoft Dynamics SL upgrade process.

Back To top

7) A signed contract must be found in two places: at the customer level & at the actual order within Order Management. Can one document be attached in two places or will it have to be scanned twice?

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