Learn Dynamics 365 Finance and Operations(Axapta)

It is a powerful feature of the Ax 2012 R2 .Just for the every installation there is a default legal entity "DAT", same there will be default partition called “Initial". and we can also make other partition too to seperate application data. Couples of the feature associated with partition are as:  It has been achieved by introducing a new table property  i.e. "SaveDataPerPartition" on the tables. A data partition helps sharing the Ax install base but not the data There can be companies with the same name in multiple partitions. Intercompany doesn’t work across partitions The companies between two partitions cannot be merged and Intercompany features cannot be used. the only option is to use Data migration tool kit for data export import between partitions we can know the current partition through ‘getcurrentpartitionrecid()’ similar to ‘curext()’ We can create company with same name in different partition. Share System Data like Batch Job, AIF port

Partitions:            • A partition is a unit of isolation in the AX database • The concept is similar to a company for company specific tables except it is applied to almost all tables – The exceptions include tables related to batch processing, enterprise portal, and services. Motivation: • A new partition can be used to isolate unit tests and their data from a deployment that has data loaded or that has been corrupted by previously running unit tests • The server team will not accept “partition bugs” that are unit test specific. In other words, unit tests are not a supported scenario, but I have not seen any problems that could not be fixed. Steps For Making Partitions: Its quit easy to make partiitions in Dynamics Ax 2012.Just follow the following steps below: Step 1:Just go to the System Administration->Setup->Partitions as senn below in the image. Step 2: Now click the partitions new form will open in that form you will see the existing partitions.You can ad

Model store database The model store is the database where all application elements for Microsoft Dynamics AX are stored. Customizations are also stored in the model store. The model store replaces the Application Object Data (AOD) files that were used in earlier versions of Microsoft Dynamics AX. Baseline model store The baseline model store holds model store tables for the earlier version of the metadata and is used only during upgrade. The baseline model store is like the old folder in earlier versions of Microsoft Dynamics AX. Note : In Microsoft Dynamics AX 2012 R2, the model store was moved into a database that is separate from the business database.

Creating number seq Today i want to describe about how to create number sequence in AX2012 It is same as like as we know in Ax2009 but small steps is added in AX2012.don't worry just follow the below steps simply we will get number sequence in AX2012. We will Take a EDT name as "Car Id" and create in number sequence.For that first we should select a module for new number sequence for example project module.                                     steps: 1.  Create an edt : CarId .      AOT >> Extended Data Types >> New  >> Properties >> Name  >> Car Id. 2. Write a code on lode module() on NumberSeqModuleProject {       datatype.parmDatatypeId( extendedTypeNum (Car Id));        datatype.parmReferenceHelp( literalStr ( "@SYS334483" ));        datatype.parmWizardIsManual(NoYes::No);        datatype.parmWizardIsChangeDownAllowed(NoYes::No);        datatype.parmWizardIsChangeUpAllowed(NoYes::No);

This post is a quick walk-through of surrogate keys, replacement keys, and field preview parts, which are new concepts in Ax2012. Overview The requirement used in this example is as follows: Have a new field on the sales order header called 'Priority'. This should point to a user-configurable table, containing a priority code and description. Before we start there are a couple of terms you need to understand: Natural key . Think of this as the  primary key that makes the most sense . eg CustTable.AccountNum and InventTable.ItemID. We can ignore the effect of DataAreaID for non-shared tables for now. Surrogate key . The surrogate key in database terms refers to a field that also uniquely identifies a record, but isn't a  natural  selector. When looking at Ax, this is the  RecID.  In other systems this could be a sequential number, or GUID. Typcially, it's something created by the database itself, like an identity column, however in Ax it's managed by

The  Financial consultant   working with the controller-ship during the analysis phase and the design phase in order to understand how will utilize the financial dimension function effectively the financial consultant was constrained with the limited number of financial dimensions, and that leads to conflict with customer, and at some points dissatisfaction,  MS Dynamics AX 2012   have bridge this critical gap where offering unlimited financial dimensions so there is no constrains. There was other obstacle facing the implementation team which is assigning master data to financial dimensions such as vendors, customers, fixed assets, items, and banks, and the best scenario for it is automatic (on line) assignment in order to keep the integrity, the solution for this requirement whether it will be maintained manually or by automatic trigger (customization) MS Dynamics AX 2012 have bridge this gab too. MS Dynamics AX 2012 has two (2) types of financial dimensions; - See more at: