Dynamics AX Retail Installation Guide – Part 2

1.Install Retail Retail Channel Database

Start Microsoft Dynamics AX Setup and select “Retail channel database” option, and then click Next

channel

Enter SQL server and database to be created.

Img3

2.Install Async Client

Start Microsoft Dynamics AX Setup and select “Async Client” option and then click Next.

Enter the URL where Async Server was installed, channel identification, local service user and password, then click Next.

Img4

The Async client will need a channel database and message store database. Enter proper the settings.

Img5

Later, you can change the Async Client settings by running C:\Program Files (x86)\Microsoft Dynamics AX\60\CDX\Async Client\Package\AsyncClientConfigurationUtility.exe

Img6

3.Install Retail POS

Start Microsoft Dynamics AX Setup and select “Retail POS” and “Retail Channel Configuration Utility” options  and then click Next.

Img7

Img8

Choose the option to create a new offline database for POS. Enter local SQL server and database.

Then select “Configure retail POS” option and check “Configure offline database”. Enter the proper settings.

Img9

4 – POS

Start POS client.

Enter user name and password to validate installation.

Img10

Advertisements

AOS Crash – Generic .NET error

Recently in a development environment I got an error in AOS that prevent it from starting. After checking the event viewer for a detailed message error, I simply got a generic error message about an invalid assembly.

Solution :

1)   Deleted all files in folder C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin\XppIL.
2)  Opened SQL Enterprise Manager and executed the following command “TRUNCATE TABLE SysXppAssembly”. This will delete compilation data.
3) Started AOS Server
4) Run a full CIL compilation.

Voila, AOS is running now smoothly.

Implementing Master Data Management (MDM) between Dynamics AX 2012 R3 and Dynamics NAV 2013

Microsoft Dynamics R3 ships with Master Data Management (MDM), a feature to synchronize master data between AX instances and other applications. MDM module handles most business requirements concerning master data: publishing, filtering, conflict management, etc.

MDM is built on top of Microsoft SQL Server Master Data Services (SQL MDS), requiring a SQL Server Enterprise Edition to work properly. Very little effort is required to publish master data records between AX instances with MDM enabled.

The goal of this post is demonstrate an approach of managing customer information centrally in AX and publishing it to other applications, in this particularly case Dynamics NAV, since many customers have various ERP’s in their environment.

A single-master configuration has implemented, only the AX 2012 instance can write to MDS, Dynamics NAV will be a read-only subscriber. This decision will eliminate the biggest issue in MDM, the conflict management.

 

Drawing1

 

Set up SQL MDS

Open SQL Server Open Master Data Services Configuration Manager

Select “Create database” and fill the database name, in this case, I have choosen MDM.

Capture2

Select “Web Configuration” and fill Website Name and then click “Create Application”. Associate database MDM with the created web application.

 

Capture3_1

Open “Microsoft Dynamics AX Management Shell” At the Windows PowerShell command prompt, execute the  command.  “Set-AXMasterDataManagementMDSSetup –MDSServerName localhost MDSDatabase MDM”

Replace server and database parameters with your values

Capture1

Set up Dynamics AX

 

Open “Data import export framework” -> Master data management -> Configure SQL Server Master Data Services connection.

 

Fill SQL Server where MDM is installed ,set database name to “MDM. In the MDS service endpoint field, enter the URL for the MDS web application, followed by /service/service.svc.

Capture4_1

 

Click “Test Configuration”.If everything is correctly configured, a success message should is displayed.

Capture5

 

Open Data import export framework -> Master data management -> Publish entities to SQL Master Data Service

Select Customer Entity and click Create schema. After the schema have been created, the checkbox  in the “In MDS” column will be checked.

Capture6

 

Open Data import export framework -> Master data management -> Manage Synchronization

Create a new sync group. Enter name and choose the proper company.

Capture7

Click Entities and then fill “customer” value in the Entity field

Capture8

Select customer entity and click Settings, take note of Subscription view because will need it later. Ajust

Capture9

Open Data import export framework -> Master data management -> Manage Synchronization

Click New schedule and define the recurrence according to your requirements.

Capture10

 

Open Data import export framework -> Master data management -> Manage Synchronization

Click Synchronization History to check if the job is running properly.

Capture11

 

Set up Dynamics NAV

Open SQL Server Enterprise Manager.
Query the SQL View DMFCustomerEntity_View in MDM database, and it should display all the customer records exported from Dynamics AX.

 

Capture12

Create a view in NAV database with the required fields from the view DMFCustomerEntity_View

Capture13

In the Dynamics NAV, create a new table with the exact same name and fields of the view DMFCustomerEntity_View. Before saving the object, select the LinkObject property to true.

CaptureNAV1

Run the table object to see all the data records. Implement a custom object to import data from this virtual table to customer table of Dynamics NAV.

CaptureNAV2

 

 

 

Dynamics AX Partner built localization – Portugal

Over the past years, Microsoft has put an enormous commitment in Dynamics AX, setting a product with a strong financial core, incorporated with several industry solutions.
The facts of this strategy, is the rapidly increasing number of Dynamics AX implementations worldwide, being one of the fastest growing ERP in the market.

In the Portuguese market, even without a localization provided directly by Microsoft, Dynamics AX have seen an healthy grow in new implementations, driven by international rollouts or even by Portuguese companies requesting an ERP capable of covering multiple countries from a single instance deployment with sort implementation times.

Localizations

Dynamics AX is R2 is localized by Microsoft in 36 Countries, to meet regulatory requirements of those countries.

Included Localizations in Dynamics AX R2

Australia, Austria, Belgium, Brazil, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, India, Ireland, Italy, Japan, Latvia, Lithuania, Malaysia, Mexico, Netherlands, New Zealand, Norway, Poland, Russia, Saudi Arabia, Singapore, South Africa, Spain, Sweden, Switzerland, Thailand, United Kingdom, United States.

The growing need of Dynamics AX in Portugal, challenges local partners providing a localization with  quality.

Changeless

A localization process, must always ensure that is up to date of the changing regulatory requirements.
One of the Portuguese regulatory requirements is invoicing customers using certified software by the Portuguese local authorities.
The certification process for example, demands that every invoice issued to customers has a cryptographic hash code. Those should be uploaded into local authorities using a local standard audit file (SAF-T).

Dynamics 2009 and 2012 are certified by local authorities to be used in Portugal.

 

Advantages
A partner built in localization has many advantages, because it provides quick responses to local regulatory requirements and a good understating on local needs.

Dynamics AX DB Entity Relationship Diagrams

Microsoft released a pack of Dynamics AX entity relationship diagrams. This pack covers most core tables of the product. For example an ERD of Customer table

These diagrams are available in http://www.microsoft.com/dynamics/ax/erd/ax2012r2/Default.htm

To help you find the correct information you also have an Alphabetical list of tables.

Erd-One-AcctRecv-M1-CustTable-vsd

 

 

You can also build by yourself these diagrams using the built in Reverse engineering tool, please check  http://msdn.microsoft.com/en-us/library/aa499193.aspx

 

Data Import/Export Framework Walkthrough: Importing data

Microsoft AX Data Import/Export Framework, out of the box supports 70 Entities types. In this post I will perform an import of customer data. The same concept is also applicable to other entities types.

Configuration

You must setup a folder with the purpose of sharing data between AOS Service and SQL SSIS.

Open “Data Import/Export Framework > Setup > Data Import/Export Framework parameters”

Screenshot01

Select a folder and press validate.

If the folder exists and has the proper permissions the icon should change to green.  AOS Services and SQL SSIS must have access permissions to this folder.

Data Source Formats

Open “Data Import/Export Framework > Setup > Source Data Formats”

Where possible I prefer using a file format that allows manipulating data directly in Microsoft Excel.

Screenshot02

  1. Create a new record.
  2. In source name, named it “TXT.
  3. Select a description that defines the data format.
  4. The files will be TAB separated values to easily manipulate it in Microsoft Excel. I have selected the option Delimited in File format and Row Delimiter type “Tab {t}”.
  5. I prefer using column names in the first line, so I have selected the “First row
    header” option.

Processing Group

Open “Data Import/Export Framework > Common > Processing Group” and select new. I only want a processing group that will import Customers, so I have named it Customers.

Select Entities option

Capture8

  1. Click New
  2. In the entity Name select “Customers”
  3. In the Source Format, select previous format, TXT file.
  4. Select “Run Business Logic in insert or update method” and “Run business Validation”

Select the option “Generated Source File”

Screenshot05.0

Press Next

Screenshot05.1

Select the fields you would like to import. To work with the proper template file, select “Generate Template”.

Capture9

Now, open the template in Microsoft Excel and fill your data.

Screenshot07

Close Excel, and select the text file in sample data.

19

Click Modify Mapping to validate the mappings and you can amend incorrect configuration

12

Select “Mappings to details” to map data using a tabular method.

Screenshot08

I have chosen the “Auto-generated option” because I want customers numbers being assigned automatically by Microsoft AX.  Confirm if everything is correct and close window.

Press “Preview Source file”

Screenshot08.1

Close “Entities Processing group window” and select “Get Staging Date” in the list of processing group.

Screenshot10

Create a new job.

Screenshot11

Select run.

Screenshot12

Press Ok.

Screenshot13

A log message is displayed.

Now, select “Copy data to Target”, to move the information from the staging area into final entities tables.

25

Select the job that was created in first step to import data into staging area and ok.

Capture10

Run the job.

Capture11

Data Validation

Open Accounts receivable > Common > Customers >All customers and filter, customers using the data in Excel.

30

Open the customer and validate the imported data.

31

Data Import/Export Framework Walkthrough: Installation

Microsoft provided an extension to Microsoft Dynamics AX that smooth’s the import / export process. Without this framework, importing data to some specific tables implied using X++.

I will try to publish a series of posts about Dynamics AX Data Import/Export Framework, covering:

  1. Installation
  2. Architecture
  3. Importing data to an out of the box target entity
  4. Importing to a custom target entity

Installation Step by Step

1 – First you must download the extension package from informationsource, unzipt it and execute setup.

2 – The installation process is split into 3 main components :

  • A component must be installed on a server running MS SQL Integration Services.
  • A component must be installed on a server running AOT.
  • A component must be installed on a workstation having the Dynamics AX client

Since I’m running all the services on a single box in a virtual machine, I have selected all components.

Install

In first step of the wizard, the installer will check if you have the minimal requirements.

Capture4

Designate a user account to run the Data Import/Export Framework service. Enter the user account of AOS service.

Capture5

Press Next.

3 – The components are now installed, now the model files must be imported into Dynamics AX

Import the Model file from a command line using AXUTIL. The modal file is located inside the folder of the client component.

Note that there is a matching folder in “C:\Program Files\ Microsoft Dynamics AX 2012 Data Import Export Framework Client Component” for each supported version of Dynamics AX.

  • AX 2012 -> Folder 2012.
  • AX 2012 Feature Pack ->  Folder 2012 FP.
  • AX 2012 R2 -> Folder 2012 R2.

For Dynamics AX 2012 R2 execute : axutil import /file: “C:\Program Files\ Microsoft Dynamics AX 2012 Data Import Export Framework Client Component \2012 R2\model\DataImportExportFramework.axmodel”

Capture7

Capture8

4 – Restart the AOS service

Capture6

5 –  Open the Dynamics AX Client, and a screen should popup to you. Select “Compile and synchronize” option. The next step is to do a full CIL compile.

Capture9

This step should take a few minutes to complete.A info log is displayed at the end.

Capture10

6 – Restart the AOS Service

Capture6

7 – Open Dynamics AX client, now the Dynamics AX Navigation pane should have the option of Data Import/Export Framework.

Capture11

Stay tuned for next posts