Learn Dynamics 365 Finance and Operations(Axapta)

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:

it is the Standard AX 2012 behaviour of the List Page forms it doesnt the override methods in the form. Here is the example - created the Form of ListPage, it doesnt allow to override the form methods.   In the case of the normal forms - it allow to override the forms methods So try by creating the form by having the  formtempate - property as None (i.e. normal form)  and try to override the form methods and then change the form property FormTemplate to ListPage  - to show a message the  override methods will be deleted  as shown in the below screen  It is the standard behaviour of AX 2012. Source - http://dynamicsuser.net/forums

Optimizing an AOS depends on what the AOS is used for. For example, an AOS that is load balanced should only allocate a certain number of resources on the server it is running on. Similarly, an AOS that is only used for the Enterprise Portal may not want to allow access to rich client users. Therefore, before taking any steps to optimize the performance of an AOS, make sure you have properly defined a role that the AOS has. There are two ways to distribute load in a Dynamics AX environment. They are the following: • Non-load-balanced cluster • Load-balanced cluster A cluster of AOSes are simply a group of AOSes. It doesn’t necessarily mean that they are load balanced. However, a load-balanced cluster does indeed mean that a group of AOSes in a cluster are load balanced. The following sections will describe in more detail what a non-load-balanced cluster and a load-balanced cluster are. Non-load-balanced cluster A non-load-balanced cluster does not have a main AOS that is dedicated

In previous versions of AX, assigning security keys was the main task for a developer. With AX 2012’s role-based security, developers play a much bigger role when creating new elements. Permissions are now assigned on the AOT elements and are grouped together in  Privileges . These Privileges  are then gathered in  Duties  which define a role. The new security framework is based on  RDPP : Roles:  a group of duties specific to a function (accountant, mechanic, clerk, manager, …)  Duties:  a group of related privileges needed for a specific task (sales order entry, approve expenses, order  picking etc,  Privileges : a group of entry points (mostly menu items) needed for a specific action (create sales order lines, set up HRM parameters, start a picking route, …) Permissions : a group of base objects  each with the required level of access (update salesTable, update HRMParameters, …) Developers are responsible to provide the appropriate privileges and permissions.  An administrat

Hi there! In AX 2012, role based security provides an extensible framework for defining access to the Microsoft Dynamics AX application and data. It changes a little bit from what we know in ax 2009. In AX 2009, administrators had to, literally, create their own user groups and manually assign users to those groups.  Also, in order give permission to a user group to execute a particular operation, the administrator had to identify objects, such as tables, fields, and menu items that were required for the operation, which was a pain in AX 2009 as identifying these elements was time consuming. However, in AX 2012, security  is role-based , and many security roles are predefined by the application to make the setup portion of it easy for us. Now, it is important to really comprehend this positive change as in role-based security, users are assigned to roles based on their responsibilities in the organization and their participation in business processes.  In fact, AX 2012 int

A primary focus in Dynamics AX 2012 was to increase a developer's productivity by automating common tasks. As part of this initiative, a new feature was introduced in Dynamics AX 2012 in the AOT. This is the creation of new forms using form templates.  If you right click on the form node, you can see an extra option there -  New Form from template As seen in the image above, you have an option to create seven different form based on the pre-defined templates, these are ListPage DetailsFormMaster DetailsFormTransaction SimpleListDetails SimpleList TableOfContents Dialog DropDialog Let us look at these in more details. ListPage  - A list page is a form that displays a list of data related to a particular entity or business object. A list page provides provisions for displaying data and taking actions on this data. Every module has at least a couple of list pages. List pages are further classified as primary and secondary list pages. A secondary list page will only

Data Partition in Ax 2012 R2:  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 Sys