6. Edit LineChart using Designer.
7. Insert a new Chart report item from the Toolbox.

8. Double click on the chart area to open the field editor, add the following fields as specified.

Field

Drop area

Year, MonthOfYearId

Category

ItemGroupId

Series

Qty

Data

9. Next, you can improve the aesthetics of the chart, as it pleases, by updating different chart properties available out of the box in Visual Studio.
10. Save, build and deploy the report.
11. Create an output menu item and bind it with the SSRS report.

12. Add menu item to Sales and marketing > Reports > Sales orders > Item sales history.
13. You should be able to see the report in the Report viewer.

Purpose:

The purpose of this document is to quickly understand the underlying data model which is used by Dynamics AX to store postal addresses for a party. Some examples of party are customer, vendor and company.

Assumptions:

Basic understanding of UML’s crow foot notation for data modeling.

Data model:

Purpose:

The purpose of this document is to describe how we can deploy automated builds to different Dynamics AX pre-production environments so that newly developed features could be rolled-out for UAT. The document also illustrates how version controlling by TFS and data migration activities fit into the big picture.

Purpose:

The purpose of this document is to illustrate how we can develop AIF document service, what are the important methods available that can be overridden to do the customization and finally how we can consume/unit test the document service through an external .NET application.

Business requirement:

Ability to integrate Dynamics AX with external systems.

Assumptions:

Application Integration Framework (AIF) has been configured to process inbound and outbound messages.

Development:

Create an AOT query. Prefix it with Axd to follow the naming convention for document service.

Run AIF document service wizard to generate/regenerate:

Document class (Axd class).

Represents whole business document.

Used to perform cross-table validations.

Serializes/deserializes the document to/from XML.

Document object class

Object interface to whole business document.

Data object classes

Object interface to underlying tables involved in the document.

AxBC classes, if chosen

Wrapper classes for underlying tables involved in the document.

Used to perform table-level validations.

For example, AxSalesLine.validateWrite method.

It then calls validateWrite method of SalesLine table.

Used by Axd class to create, read, update, delete data in tables.

Service class

Contains the service operations in the form of methods.

Service node

Exposes service operations to inbound/outbound ports

Change namespace property of service node (optional).

Generate incremental CIL.

Register the service

Create security privilege for each service operation (optional).

Create an enhanced inbound port

Choose an adapter

File system adapter

HTTP

ISABEL SEPA credit transfer

MSMQ

NetTcp

Windows Azure Service Bus

Choose service operations

Activate

Important methods:

Axd class

prepareForSave/prepareForSaveExtended method

Validation code goes here.

For example checkSalesTable method in AxdSalesOrder class.

updateNow method

Business logic to be executed post insert/update of document.

For example, post receipt in II7.

expandSurrogateForeignKeys method

To automatically resolve surrogate foreign keys to natural keys.

getSurrogateForeignKeyValue method

To manually resolve surrogate foreign keys to natural keys.

AxBC class

initMandatoryFieldsExemptionList method

To make a field optional which is mandatory at the table level.

initMandatoryFieldsMap method

To make a field mandatory which is optional at the table level.

set<Field> method

To set default value of a field in service.

This method calls parm method to set the default value.

For example, setLineNum method of AxSalesLine class.

It calls parmLineNum method of AxSalesLine class.

Consuming service:

Create console application in Visual Studio

Add service reference

Sometimes, setting some fields doesn’t work in C#. We use “<Field>Specified” parameters for them.

Purpose:

The purpose of this document is to describe how we can add custom fields to standard DIXF target entity. While performing data migration for standard entities like customer, we often come across a requirement to load data for customized fields as well. In this post, we will add custom fields of customer master to its standard DIXF entity.

5. Make sure the same fields exist in the target entity, CustTable table.
6. Open Data import export framework > Setup > Target entities7. Create new target entity as follows. You must create a new target entity to include the newly added fields.

8. Verify the newly added fields by looking at the mappings.

9. Create new processing group and select the newly created target entity