AMC Consult A/S May 9, 2019 Banking 2012 v6

INSTALL GUIDE

AMC BANKING FOR MICROSOFT DYNAMICS AX 2012

| Introduction 2

CONTENTS

1 Introduction................................................................................................................................... 3

2 Distribution .................................................................................................................................... 4

3 Installation ..................................................................................................................................... 5

3.1 Prerequisites.......................................................................................................................... 5

3.2 Installation ............................................................................................................................. 5

3.2.1 Install the Banking model ....................................................................................... 5

3.2.2 Verify the installation ............................................................................................. 6

3.2.3 Compile the module ............................................................................................... 8

3.2.4 Synchronize the database (1st time) ....................................................................... 9

3.2.5 Execute update scripts ........................................................................................... 9

3.2.6 Synchronize the database (2nd time) .................................................................... 10

3.2.7 Deploy reports ...................................................................................................... 10

3.2.8 Add Banking menu ............................................................................................... 11

3.2.9 Generate Full CIL .................................................................................................. 11

3.2.10 Restart AOS server(s) ............................................................................................ 11

4 License setup ............................................................................................................................... 12

4.1 Registration ......................................................................................................................... 12

4.2 Test connection ................................................................................................................... 12

5 Troubleshooting .......................................................................................................................... 14

5.1 Label issues .......................................................................................................................... 14

5.2 Insufficient memory ............................................................................................................ 14

5.3 Proxy .................................................................................................................................... 15

6 API ............................................................................................................................................... 17

6.1 Bank account form link ........................................................................................................ 18

6.1.1 Customer to bank account link ............................................................................. 18

6.1.2 Vendor to bank account link ................................................................................ 19

6.1.3 Avoid workflow circumvention ............................................................................ 20

6.2 Auto create bank accounts .................................................................................................. 22

7 US Localizations ........................................................................................................................... 23

7.1 Installation ........................................................................................................................... 23

| Introduction 3

1 INTRODUCTION Thank you for choosing AMC Banking for Microsoft Dynamics AX 2012. We hope you enjoy using the

module and its facilities.

If AMC Banking fails to meet your expectations, you are welcome to contact your reseller or us directly.

We appreciate your feedback, as it allows us to optimize the module’s facilities and user interface. We

work closely with both partners and customers to provide you with a module of the highest standards.

For further info, please visit our website www.amcbanking.com, where you can find information on

our company, the Banking module as well as all our other products.

Best regards

The development team

AMC-Consult A/S

| Distribution 4

2 DISTRIBUTION The Banking module is distributed in a standard Dynamics AX 2012 model and is cumulative, meaning

that it is enough to install a single model file to install the complete version of the latest Banking

module.

To get the latest version of the Banking module model, please visit:

https://amcbanking.com/support/amc-banking/microsoft-dynamics-ax/download/version-2012

| Installation 5

3 INSTALLATION

3.1 PREREQUISITES

Before you start the installation process, please ensure that you meet the requirements below:

1. You have the latest version of the Banking model file.

2. You have the necessary security access rights to the AX 2012 AOS server, the database as well

as the SQL Reporting Server (admin rights are needed).

3. You have the possibility and permission to stop and start the AOS server during installation.

! You have read the readme file that accompanies the installation package. This is especially

important, if you are updating an existing Banking installation, as it contains vital information

on potential data issues etc., which you might experience, when moving between two Banking

versions.

3.2 INSTALLATION

We recommend that Microsoft Dynamics AX 2012 Management Shell is used to install the Banking

model. For more info, please visit:

http://msdn.microsoft.com/en-us/library/hh335181.aspx

3.2.1 INSTALL THE BANKING MODEL

Before starting the installation process, please ensure that all AOS instances are stopped. This ensures

that all elements, labels etc. are installed, updated and refreshed correctly during the installation.

1. Stop all AOS service instances. This ensures the all Banking elements and labels are installed

and refreshed correctly

2. On the AOS server, go to Administrative Tools

3. Start Microsoft Dynamics AX 2012 Management Shell

| Installation 6

4. In the shell window, type the install-axmodel command and press Enter. Remember quotes

around then file name if it contains spaces

Example: Install-AXModel -File "c:\amc-banking 2012.5.2.0" -nooptimize -noprompt -conflict overwrite

5. Once the installation is successfully finished, type Exit and press Enter

6. Start the AOS service instances again

3.2.2 VERIFY THE INSTALLATION

To verify and finish the installation, start an AX client as an administrative user. Once the client has

started, you will be prompted with the following notice, telling you that the AX model store has been

modified.

Though the notice emphasizes, that the Skip option is not recommended, the Skip option is enough

for finishing the Banking installation. Press OK

Open the Development Workspace by pressing CTRL+D, and complete the following steps of

verification:

| Installation 7

✓ VERIFY INSTALLED MODEL

Go to Tools > Model management > Models installed, to ensure that the AMC Banking 2012

Foundation model has been updated.

The AMC Banking 2012 Foundation model’s version number should correspond with the

version number of the model file you have just installed.

✓ VERIFY MAPPINGS

To utilize and benefit from a lot of standard journal related functionality, the Banking

module implements the standard AX journal interface. To do so, the Banking module

requires Banking specific mappings to be added.

Ensure that each of the three journal maps, JournalNameMap, JournalTableMap and

JournalTransMap, have Banking related mappings added

✓ VERIFY WEB SERVICE CLIENT

For the Banking module to communicate with the web service, which handles the conversion

of bank files, the Banking module requires that the SOAP client AmcBankSoap.dll is available

from the client, from which the compile is executed.

The SOAP client should automatically be created, yet please ensure that the

AmcBankSoap.dll exists in the AOS server’s VSAssemblies folder

Example: e.g. C:\Program Files\Microsoft Dynamics AX\60\Server\<instance>\bin\VSAssemblies\

| Installation 8

3.2.3 COMPILE THE MODULE

Once the version has been verified, the module should be compiled. To do so, please open Projects by

pressing CTRL+SHIFT+P.

Find and open the public project AmcBanking_2012_v5. Compile the complete project from the

opened project form.

The compiler should finish without raising any compile errors, warnings or Best Practice errors, but

the following warning could occur anyway

MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and

the processor architecture of the reference "Microsoft.Dynamics.AX.ManagedInterop", "x86". This mismatch

may cause runtime failures. Please consider changing

The warning relates to the C# project AmcBankSoap, which is included in the Banking model. The C#

project is responsible for web service communication and is set to be deployed on the server. For the

server to execute the C# code, it needs to be built in x64 (64 bit). The compiler though runs on the

client, which is executed in x86 (32 bit), and therefore it mistakenly thinks a processor architecture

mismatch has occurred.

Since the client will never execute code from the AmcBankSoap C# project, the warning can safely be

ignored.

| Installation 9

3.2.4 SYNCHRONIZE THE DATABASE (1ST TIME)

Synchronize the database to create new, modify existing and delete old Banking tables from the

database.

Open the AOT (CRTL+D) and select Data Dictionary. Right click and select Synchronize.

Please note, that if you are updating from an old version of Banking, you might experience errors

during the databases synchronization, like the ones below

If such errors should occur, you do not need to worry. These are expected and will be solved by

completing the next step, executing update scripts, as described in the next section.

3.2.5 EXECUTE UPDATE SCRIPTS

If the Banking module is being updated from an earlier version, we highly recommend running the

included update scripts, which converts and corrects data throughout the module, and thereby helps

ease the update process.

To execute the update scripts, open the Application Object Tree (CTRL+D), locate and right-click the

class AmcBankDataUpgrade and select the “Open” option. In the dialog, the individual scripts can be

chosen before clicking the OK button, which will then execute the selected upgrade scripts.

| Installation 10

We recommend, that all upgrade scripts are executed each time the Banki ng module has been updated. All

upgrade scripts have been carefully crafted in a way, that allows them to be executed multiple times, while

sticking to only upgrading relevant data.

3.2.6 SYNCHRONIZE THE DATABASE (2ND TIME)

Synchronize the database again to finalize the remaining database changes, which could not be

completed prior to the update script execution.

Open the AOT (CRTL+D) and select Data Dictionary. Right click and select Synchronize.

3.2.7 DEPLOY REPORTS

The Banking module includes SSRS reports, which should be deployed to the SQL Reporting Server.

Open the AOT (CRTL+D) and select / SSRS Reports /Reports. Select all AmcBank* reports, right click

and select Deploy Element.

If successfully deployed, AX will confirm the successful deployment in the infolog

| Installation 11

3.2.8 ADD BANKING MENU

It is necessary to create the AMC Banking menu tab manually in the main menu, to avoid the risk of

overwriting existing menu adjustment.

Notice, that the existing main menu object may have been adjusted in a higher AX layer. In that case,

you must switch to this layer before added the Banking menu reference to the MainMenu.

Right click the MainMenu menu and select New > Menu Reference. Drag and drop the AmcBankMenu

from the opened MenuReference form to the MainMenu object. If you then want to move the menu

item, it can be done with ALT + arrow up / arrow down. Save your changes by right-clicking on the

Main Menu and select Save.

Close and restart Dynamics AX. Verify that you now have a new menu named AMC Banking.

3.2.9 GENERATE FULL CIL

With the code having been compiled client-side and, the next step is to ensure that the code being

executed server-side on the AOS server(s) has also been added or updated. To do so, open the

development workspace (CRTL+SHIFT+W) and choose Build > Generate Full CIL.

3.2.10 RESTART AOS SERVER(S)

The final step of the installation process is to restart the AOS server(s). Labels, the web service client

object etc. is (re)created during start-up of the AOS server, hence this step is very important to ensure

that the updated code is being properly used.

| License setup 12

4 LICENSE SETUP To use AMC Banking, a valid license must be present. If an existing license is not present, a new license

must be registered.

4.1 REGISTRATION

To register a new license open AMC Banking > Setup > Parameters. In the parameter setup, open the

About tab and click Get started, which opens the license registration landing page, from which the

Banking module can be registered.

Once the license has been registered, enter the username and password that corresponds with the

registered license and change the URL, if you are using a dedicated conversion web service.

4.2 TEST CONNECTION

The Test connection button on the Web service tab, can be used to test the connectivity against the

bank data conversion web service. In addition to testing the ability to reach the endpoints of the bank

data conversion service and the license server, username and password is also verified and the SSL

certificate status is updated.

| License setup 13

If everything is successful, the system should return a message like the one below

If Test connection instead returns an error, it indicates, that a connection could not be established.

Please, carefully read the error message to pinpoint the exact nature of the problem.

Always ensure that firewalls etc. allows outbound access to the bank data conversion service address

specified in the URL field

| Troubleshooting 14

5 TROUBLESHOOTING

5.1 LABEL ISSUES

If the installation fails with an error, saying that labels already exist, please delete the existing

Banking label files (axABA*.*) from the AOS application folder and shut down all AOS service

instances.

Example: C:\Program Files\Microsoft Dynamics AX\60\Server\<instance>\bin\Application\Appl\Standard

Once the label files have been deleted, the installation should be able to finish successfully. The label

files will be (re)created, when the AOS service is started again

If label related issues, like missing labels, occur after the deletion of label files and restart of the AOS

service instances, a CIL compilation will usually do the trick. Once the environment has been

successfully CIL compiled, restart the AOS service(s).

5.2 INSUFFICIENT MEMORY

Though the new Banking version’s memory consumption has been drastically improved, there is

always a risk that a memory related error, like the following, could occur.

(en-us = Error executing code: Insufficient memory to run script.)

| Troubleshooting 15

This error occurs because the internal AX buffer limit has been exceeded. To solve the issue, the buffer

limit needs to be extended, using the following steps:

1. On the AOS server(s), click Start, type regedit.exe and click Enter 2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dynamics Server\6.0\instance

name\config name 3. Add a new key with the name maxbuffersize (lower case letters only) and set a suitable value for this.

We recommend an initial value of 40, but you may need to set it higher.

4. Restart the AOS service(s).

5.3 PROXY

AMC Banking communicates with the web services from the AOS server. If your company is using a

proxy server on the AOS server, it will result in errors, when executing web requests.

GENERAL PROXY SETUP

To solve the problem, it requires a setup of Windows default proxy settings (WinInet) on the AOS

server. This can be done in the following way:

1. On the AOS server(s), start Internet Explorer

2. Go to Tools > Internet Options

3. On the Connections tab, click LAN settings

4. Click the Use a proxy server for your LAN to activate proxy server use

5. Enter the required proxy settings for your environment and click OK

PROXY SETUP ON WINDOWS SERVER 2003 AND OLDER

1. On AOS server(s), click Start, type cmd.exe and press Enter

| Troubleshooting 16

2. Type proxycfg -u

If you need to remove the proxy settings from WinHTTP, you can use the command proxycfg -d. For more information about Proxycfg.exe, visit:

http://support.microsoft.com/kb/289481

PROXY SETUP ON WINDOWS SERVER 2008 OR LATER

1. On AOS server(s), click Start, type cmd.exe and press Enter 2. Type netsh winhttp import proxy ie

If you need to remove the proxy settings from WinHTTP, you can use the command netsh winhttp

reset proxy. For more information about Netsh.exe, visit:

http://technet.microsoft.com/en-us/library/cc731131(WS.10).aspx

| API 17

6 API We have developed an API, containing supplementary methods, which allows a more seamless and

improved interaction between the Banking module and standard AX functionality.

The API consists of optional modifications to standard AX objects. To ensure that the API does not

conflict with other modifications, we therefore recommend that an experienced Dynamics AX

developer or consultant do the implementation of the API.

Furthermore, we recommend that a backup of the elements concerned, be done, prior to the

modifications.

As the API consists of optional modifications, which are not part of the standard Banking distribution,

AMC-Consult will not be held responsible for any consequences of these modifications in AX. In

addition, the modification described in the section, are not covered by AMC-Consult’s general support

agreements for AMC modules.

Unless stated otherwise, this section is based on the latest versions of both Banking and Dynamics AX

2012.

| API 18

6.1 BANK ACCOUNT FORM LINK

As you have installed the Banking module, you are likely to use the payment facilities and thereby the

customer and/or vendor bank accounts at some point.

The Banking module contains a range of supplementary, payment related setup fields to standard AX’s

bank account setup. These fields are not visible in standard AX’s own bank account setup form, hence

can only be configured in the Banking module’s own bank account form.

Therefore, it will likely be a good idea to add a link from the customer and vendor forms to the Banking

module bank account forms.

6.1.1 CUSTOMER TO BANK ACCOUNT LINK

To add a link between the standard AX customers and the AMC Banking bank account setup form,

simply add the AmcBankCustBankAccounts display menu item to the form CustTable/

CustTableListPage form, e.g. by dragging the menu item to the form, like shown below:

Though not required, we recommend that you right-click the menu item and specify the properties

shown below, which will make it easy to distinguish the menu item from standard AX’s own bank

account menu item

| API 19

Once the menu item has been added and the properties has been adjusted, as shown above, the menu

item should appear in the customer forms’ menus

6.1.2 VENDOR TO BANK ACCOUNT LINK

To add a link between the standard AX vendors and the AMC Banking bank account setup form, simply

add the AmcBankVendBankAccounts display menu item to the form VendTable/VendTableListPage,

e.g. by dragging the menu item to the form, like shown below:

Though not required, we recommend that you right-click the menu item and specify the properties

shown below, which will make it easy to distinguish the menu item from standard AX’s own bank

account menu item

| API 20

Once the menu item has been added and the properties has been adjusted as shown above, the menu

item should appear in the vendor forms’ menus

6.1.3 AVOID WORKFLOW CIRCUMVENTION

The bank account approval workflow, which is included in the module, is used to prevent fraud etc.,

by restricting users from changing vendor bank accounts.

Since the workflow is tied to the bank account forms in Banking, users would be able to circumvent

the restrictions of the workflow, by entering standard AX’s own bank account forms instead. If you

plan to use the bank account approval workflow, we therefore recommend, that you add the following

code-wise measures, to block off users from standard AX’s bank account forms.

! Delete or hide the bank account menu items from the customer and/or vendor setup.

Remember to do this in both the master data forms as well as the list page forms.

! Add or replace bank account fields’ jumpRef methods in the master data form data

sources (see below)

| API 21

FORMS\CUSTTABLE\DATASOURCES\FIELDS\BANKACCOUNT\METHODS\JUMPREF: public void jumpRef() { AmcBankAPI::jumpRefBankAccount(CustTable, this); }

FORMS\VENDTABLE\DATASOURCES\FIELDS\BANKACCOUNT\METHODS\JUMPREF: public void jumpRef() { AmcBankAPI::jumpRefBankAccount(VendTable, this); }

| API 22

6.2 AUTO CREATE BANK ACCOUNTS

This modification will result in the AX system automatically asking users to add payment information,

when adding new customers or vendors.

To implement this functionality, find the VendTable form (or any Form with a CustTable or a VendTable

data source will do) and edit the VendTable data source’s “write” method.

In the existing method, insert the following code (marked with green comments):

void write() { // AMC Banking --> boolean newRecord = vendTable.RecId ? NoYes::No : NoYes::Yes; // AMC Banking <-- dimensionDefaultingController.writing(); element.numberSeqFormHandler().formMethodDataSourceWrite(); vendTable.Party = dirPartyTable.RecId; partyForm.writeAddressBookParty(); super(); // AMC Banking --> if (newRecord) AmcBankAPI::addBankAccount(vendTable); // AMC Banking <-- }

Once the API changes have been implemented, the users will be prompted with the dialog below,

when adding new vendors

| US Localizations 23

7 US LOCALIZATIONS As of Banking 2012.4.3.0, we introduce a US localizations add-on model, which can be installed once

the Banking foundation model has been installed. The US localizations e.g. includes the possibility to

create Positive Pay cheque confirmation files.

The US localizations are only available on R3 vers ion, as the model interacts with standard cheque and

positive pay functionality, which were first introduced in R3.

7.1 INSTALLATION

The installation is very like the foundation model installation’s steps 3.3.1 to 3.3.4, but in addition,

please also verify that the US localization model number corresponds with the Foundation model’s

equivalent number. The first three numbers in the version number of the two models should be

identical.

Once the US model has been successfully compiled and tables has been synchronized, finish the

installation by adding the AmcBankPositivePayJournalTable manually to the Banking menu, like shown

below.

| US Localizations 24

The added menu item will work as the point of entry for Positive Pay functionality in the Banking

module and will show up once the AX client has been restarted.