Microsoft Dynamics AX Overview

Microsoft Dynamics is a unique Business Solution provide by the Microsoft Team. The Microsoft Dynamics is totally an ERP (Enterprise Resources Panning) solution used by many companies and industries world wide. Dynamics AX is not just an ordinary software solution for any business solution, it's provide a compact, business oriented solution in which developer can develop out of the box business logic/requirements.

Microsoft Dynamics AX Modules

Dynamics AX is such a powerful tool which contains 19 CORE Modules in it.

Following are the list of the modules Dynamics AX contains according to it's versions:

Traditional core (since Axapta 2.5)

• General Ledger – ledger, sales tax, currency, and fixed assets features

• Bank Management – receives and pays cash

• Customer Relationship Management (CRM) – business relations contact and maintenance (customers, vendors, and leads)

• Accounts Receivable – order entry, shipping, and invoicing

• Accounts Payable – purchase orders, goods received into inventory

• Inventory Management – inventory management and valuation

• Master Planning (resources) – purchase and production planning

• Production – bills of materials, manufacturing tracking

• Product Builder – product mode creation and maintenance

• Human Resources – employee information

• Project Accounting – projects creation and tracking (primarily from an accounting perspective)

• Basic – data configuration

• Administration Module – system configuration

• Procurement and Sourcing

• Sales and Marketing

• Call Center - employees take orders over the phone and are able to create sales orders

• General Ledger - the ability to transfer opening balances in balance sheet accounts to a new fiscal year

• Inventory and Warehouse Management - compare item prices, enhanced posting routine and a new Inventory aging report

• Master Planning - estimate future demand and create demand forecasts based on transaction history

• Procurement and Sourcing - create your own solicitation request for RFQs, and more

• Production Control - a new option to automate material reservations

• Project Management and Accounting - new on-account billing rules and fee transactions that modify invoice proposal sales prices

• Public Sector - now able to publish a request for quotation (RFQ) to the Vendor portal and now have the ability to view details of closed RFQs

• Retail - commerce Data Exchange, updated retail server, new retail hardware station, and more

• Sales and Marketing - register serial numbers during sales processes when preparing the packing slip or the sales order invoice

• Transportation Management - plan transportation for inbound and outbound shipments, configure rating structures and view driver check-in and check-out history

• Trade Allowance Management - define merchandising events, manage trade fund budgets, process customer payments (including deductions, and more

• Warehouse Management - configure inbound and outbound intelligent workflows, use scanners/mobile devices to optimize precision in the picking and put-away processes, and more

Extended core

• Shop Floor Control

• Cost Accounting

• Balanced Scorecards

• Service Management

• Expense Management

• Payroll Management

• Environmental Management

External components

• Enterprise Portal for Dynamics AX (built on Sharepoint Services)

• Microsoft SQL Reporting Services integration

• Microsoft SQL Analysis services (KPIs)

• Project Server Integration

• WorkFlow

• Application Integration Framework (Webservices + Biztalk adapter)

• A .Net Business Connector for third-party software (A COM adapter is also available)

• Microsoft Dynamics Mobile 1.5 development tools

• Microsoft Project Client

• Microsoft Excel

• Microsoft Word

• Office 365

AX 2012 - Get default financial dimension values through X++ code

There are many areas in AX where "Default Financial Dimension" is used.In many cases we have to show the default financial dimension and its values in either forms or reports,so the key thing is that how do we get the default financial dimension and its value associated to a particular entity though X++ code.Here is the code snippet that will meet your needs.

    DimensionAttributeValueSetStorage    dimStorage;

    HcmPositionDefaultDimension          HcmPositionDefaultDimension;

    DimensionAttribute  DimensionAttribute;

    Counter                                               i;

    DimensionAttribute          dimAttr;

    DimensionAttributeValue     dimAttrValue;

    Common                      common;

    DictTable                   dictTable;

    str                         Name;

    str                         value;

    HcmPositionDefaultDimension = HcmPositionDefaultDimension::findByPositionLegalEntity(5637144830,CompanyInfo::find().RecId);

    dimStorage = DimensionAttributeValueSetStorage::find(HcmPositionDefaultDimension.DefaultDimension);

    for (i=1 ; i<= dimStorage.elements() ; i++)

    {

        select firstonly dimAttrValue

        where dimAttrValue.RecId == dimStorage.getValueByIndex(i)

        join dimAttr

            where dimAttr.RecId == dimAttrValue.DimensionAttribute;

        if (dimAttr && dimAttrValue)

        {

            dictTable = new DictTable(dimAttr.BackingEntityType);

            common = dictTable.makeRecord();

            if (common.TableId)

            {

                select common where common.(dimAttr.KeyAttribute) == dimAttrValue.EntityInstance;

                name = common.(dimAttr.NameAttribute);

                value = common.(dimAttr.ValueAttribute);

            }

        }

        info(dimAttr.Name +"----" +value + "----"+name);

    }

SSRS AX 2012 Error: Element ':PurchPurchaseOrder.Parameters.IsPurchConfirmationRequestJournal' has already been defined. To correct this, rename one or more of the model elements so that they have a unique name.

When we customize PurchPurchaseOrderReport to add a field on PurchPurchaseOrder Dataset in AOT and refresh dataset in Visual Studio.

We will get following error message:
Element':PurchPurchaseOrder.Parameters.IsPurchConfirmationRequestJournal’ has already been defined. To correct this, rename one or more of the model elements so that they have a unique name.


This is very common error and we can fix it by doing following steps: 

1. Prior to refreshing Dataset, we have to rename the parameter IsPurchConfirmationRequestJournal to IsPurchConfirmationRequestJournalDelete
2. Change the following properties:
   1. nullable – True
   2. allow blank – True
3. Now refresh the dataset you should not see any errors and a new parameter IsPurchConfirmationRequestJournal will be created. Now set the below properties of new parameter:
   1. allow blank – True
   2. Nullable – True
4. Once the properties are set, now delete the parameter ‘IsPurchConfirmationRequestJournalDelete’.
5. Rebuild the solution and deploy the report.