Layers in AX 2012

Layers in AX 2012

In Microsoft Dynamics AX, a layer system is used to manage elements.
The USR layer is the top layer and the SYS layer is the bottom layer,
and each layer has a corresponding patch layer above it.

Microsoft Dynamics AX Job profiles for Freshers and experience

Microsoft Dynamics AX Job Profiles for Freshers and experience.

To start with Job Profiles/Roles:

We have

1. Microsoft Dynamics AX Developers  (Called Technical Resource in Microsoft Dynamics AX Environment/Company)
2. Microsoft Dynamics AX Functional  (Called Functional Resource in Microsoft Dynamics AX Environment/Company)
3. Microsoft Dynamics AX Administrator (Called AX Administrator in Microsoft Dynamics AX Environment/Company) 

Skill needed for AX Technical/AX Developers :

1. X++
2. MorphX
3. SQL
4. Oops Knowledge
5. Reporting Tools like X++ and SSRS
6. Management Reporter in AX 2012
7. SSAS/Cubes in AX 2012
8. Visual Studio
9. Windows OS

Custom AX development and modification is done with its own IDE, MorphX, which resides in the same client application that a normal day-to-day user would access, thus allowing development to take place on any instance of the client. Since the Dynamics AX 2012 version, development can also be performed in Microsoft Visual Studio 2010 through a Visual Studio plugin.

MorphX is an integrated development environment in Microsoft Dynamics AX that allows developers to graphically design data types, base enumerations, tables, queries, forms,menus and reports. In addition to design of application objects, it also allows access to any application code by launching the X++ code editor.

Because MorphX uses referencing to link objects together, changes in, for example, datatypes of fieldnames will automatically be reflected in all places where they are used (such as forms or reports). Furthermore, changes made through MorphX will be reflected in the application immediately after compilation.

Microsoft Dynamics AX also offers support for version control systems (VCS) integrated with the IDE, allowing collaboration in development. There is also a tool for reverse-engineering table structures and class structures to Visio. The actual implementation limits the practical use of both these features.

X++ itself is the programming language behind MorphX, and belongs to the curly brackets and .-operator class of programming languages (like C# or Java). It is an object-oriented, class-based, single dispatch language. X++ is a derivative of C++ (both lack the finally keyword for example) to which garbage collection and language-integrated SQL queries were added.

Contribute to the technical set-up and execution of Dynamics AX project work streams
Demonstrate the ability to work systematically and logically to analyze situations, resolve problems, identify causes and anticipate implications
Maintain regular contact with customers to anticipate, identify and respond to their needs and expectations
Prioritize work and spend time on most important, value-adding areas
Play a leadership role in estimating, developing, testing and delivery of the desired software architecture.
Monitoring the performance, quality, budget and time are essential and belong in part to your responsibility.
Establish test plans and develop customer-specific customizations in Dynamics AX

Minimum Requirements:
5+ years of Dynamics AX project experience preferably working as a development lead for at least one global/complex (multiple ISV solutions / work streams) deployment.
Working knowledge of programming methodologies, structures, and concepts
.Net framework, UML, XML, SharePoint, BizTalk
10+ years working with an object oriented development language
X++, C++, C#, VB.NET, Java, .NET framework
Experience with Dynamics AX Trace Parser.
Experience with the diagnosis of X++ code tracing with performance analysis outcomes and recommendations.
5+ years as a senior X++ developer working with large development projects.
Experience with offshore management of large X++ development projects.
Working knowledge of database design and SQL (Query Language)
Have experience in estimating development effort.
Current certifications in Dynamics AX Development Introduction and MorphX Solutions Development
Working knowledge of Microsoft platform skills
Ability to lead consultants in various project work streams
Ability to manage off-shore development efforts
Willingness to learn in a fast-paced business environment
Bachelor's Degree in Computer Science, Computer Engineering, MIS, a related field, or equivalent experience

Preferred Requirements:
Development experience with other ERP products (SAP, Oracle, etc.)
Working knowledge of Microsoft Project
Industry-specific knowledge is a plus preferably (Services Industries)

Role/Responsibilities of the Dynamics AX Functional Consultant:

Since there are more than 15 modules in Dynamics AX, so it depends on person to get training or JD of HRM, T&L, Projects or AP\AR to name few.

- Collaborate with the client and project team to gather a deep understanding of the client's business, business operations and business needs to develop requirements for the customization and implementation of Microsoft Dynamics AX

- Ability to understand, communicate, and interpret client business processes and requirements

- Perform gap analysis between Dynamics AX functionality and client's requirements

- Assist in creating the different phases of the solution map for the implementation

- Participate in the entire full cycle of implementation, including quality assurance and testing of the new application.

Unable to deploy AX 2012 Reporting Extensions on SQL Server 2012 Reporting Server

Unable to deploy AX 2012 Reporting Extensions on SQL Server 2012 Reporting Server

We came across an issue where we had:

- a new server that never had Microsoft SQL Server 2008/2008 R2 or SQL Server 2012 ever installed

- we were using a Microsoft Dynamics AX 2012 Installation files from a network share to install the AX Reporting Extensions

- In the updates folder inside the installation share, we had a folder containing the extracted contents of SQL Server 2012 Compatibility hotfix

However the Reporting Extensions fail to install, and we get the following error in the DynamicsSetupLog.txt file:

An error occurred during setup of Reporting Services extensions.
Reason: Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SqlServer.BatchParser, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'

  

To resolve this issue we downloaded and installed the following two components from the SQL Server 2008 R2Feature Pack :

(1) Microsoft® SQL Server® 2008 R2 Shared Management Objects (SMO)

(2) Microsoft® System CLR Types for SQL Server® 2008 R2 (required package for SMO)

Both of this you can search and download from:  Microsoft® SQL Server® 2008 R2 Feature Pack -http://www.microsoft.com/en-us/download/details.aspx?id=16978

For more info:

http://blogs.msdn.com/b/axsupport/archive/2012/06/26/unable-to-deploy-ax-2012-reporting-extensions-on-sql-server-2012-reporting-server.aspx?wa=wsignin1.0

Table Relations Normal Related Field Fixed Field Fixed in AX 2012

Table Relations (Normal , Related Field Fixed , Field Fixed) in AX 2012

Table Relations (Normal, Related Field Fixed, Field Fixed)

Lets say you have ClothesTable and ClothesOrders.
ClothesTable has the following fields: ClotheId, Name and CollectionTypeId
ClothesOrder has the following fields: OrderId, ClotheId, Qty OrderId could be a number sequence and Qty entered manually by the user.

CollectionTypeId has the following elements:
0 - Men
1 - Women
2 - Children 
Example 1: Related Fixed FieldOn MenClothesOrder we create a new relation to ClothesTable and specify the following two:
1. Normal = ClotheId to ClotheId (Best practice to specify this on the EDT) and 
2. Related Fixed Field 0 = ClothesTable.CollecTionTypeId.
This shows that the lookup to the clothes table should show only clothes with the same ClotheId (point 1) AND clothes that are of type Men (point 2) because the table deals with order for mens' clothes. We use 0 because Men is element 0 in the Enum.

Example 2: Fixed Field This kind works the other way round:

Imagine you have a ClothesOrders table (generic) and you have seperate tables for MenClothesTable, WomenClothesTable and ChildrenClothesTable. Fixed field says that the specified normal relation (on ClotheId) to MenClothesTable only works if the CollectionTypeId of the current record is set to 0 (Men) else the relation is disabled.

We use Fixed Field relation when we have 1:N relation. On certain condition one of the relation become active & other will remain deactivate. Let me use the same theme as MSDN - Clothing.

Lets say you have 4 tables

1. ChildernClothesTable
2. MenClothesTable
3. WomenClothesTable
4. ClothesOrdersTable

Create BaseEnum CollectionTypeId with the following elements:

0 - Men
1 - Women
2 - Children

Create Extended DataType CollectionTypeEDT of BaseEnum CollectionTypeId. Now use this EDT in your ClothesTable.

ClothesOrdersTable has the following fields:

1. ClotheId,
2. Name ,
3. CollectionTypeId and

4. Qty

ChildernClothesTable, MenClothesTable and WomenClothesTable has the following fields:
1. ClotheId,
2. Name

Case 1:

On ClothesOrdersTable we create a new relation to MenClothesTable and specify the follwing two relations:

1. Normal = ClotheId to ClotheId and

2. Fixed Field ClothesOrdersTable.CollecTionTypeId = 0 and SourceEDT = CollectionTypeEDT


This shows that the lookup to the MenClothesTable should show all clothes with the same ClotheId (Define in Normal Relation) AND clotheId will only bring from MenClothesTable as we are using type Men (Define in Fixed Field Relation) because we want to activate relationship for mens' clothes. We use 0 because Men is element 0 in the Enum.

Case 2:


On ClothesOrdersTable we create a new relation to WomenClothesTable and specify the follwing two relations:

1. Normal = ClotheId to ClotheId and

2. Fixed Field ClothesOrdersTable.CollecTionTypeId = 1 and SourceEDT = CollectionTypeEDT


This shows that the lookup to the WomenClothesTable should show all clothes with the same ClotheId (Define in Normal Relation) AND clotheId will only bring from WomenClothesTable as we are using type Women (Define in Fixed Field Relation) because we want to activate relationship for Womens' clothes. We use 1 because Women is element 1 in the Enum.

Case 3:


On ClothesOrdersTable we create a new relation to ChildernClothesTable and specify the follwing two relations:

1. Normal = ClotheId to ClotheId and

2. Fixed Field ClothesOrdersTable.CollecTionTypeId = 2 and SourceEDT = CollectionTypeEDT


This shows that the lookup to the ChildernClothesTable should show all clothes with the same ClotheId (Define in Normal Relation) AND clotheId will only bring from ChildernClothesTable as we are using type Childern (Define in Fixed Field Relation) because we want to activate relationship for Childern clothes. We use 2 because Childern is element 2 in the Enum.

Hope it will help you to understand Fixed field Relation in Dynamics AX.........

Happy DAXing...... :)

XPO Link:

http://1drv.ms/1l2VEnF

Other Help on PDF:

http://1drv.ms/1l2Vs7R

Table Relations (Normal , Related Field Fixed , Field Fixed) in AX 2012

Table Relations (Normal , Related Field Fixed , Field Fixed) in AX 12

Model Management in AX 2012,Working with Models in AOT

Model Management in AX 2012 and Working with Models in AOT for Ax 2012
Procedure: Manage Models
To show the options for AxUtil.exe, follow these steps: 1.     Open Start > All Programs > Accessories > Command Prompt. 2.     Enter the following commands to open the appropriate directory. a.     Type "cd\" and then press Enter. b.     Type "cd\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin" and then press Enter. NOTE: The default path for axutil.exe is <drive>:\Program Files\Microsoft Dynamics AX\60\Server\<InstanceName>\Bin folder. 3.     Type "AxUtil.exe -?" and then press Enter to list all of the commands available in the AxUtil.exe.
Procedure: Create a Model
To create a new "CONTOSOAX" model in the user, follow these steps: 1.     Open Start > All Programs > Accessories > Command Prompt. 2.     Enter the following commands to open the appropriate directory. a.     Type "cd\" and then press Enter. b.     Type "cd\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin" and then press Enter. 3.     Type "AxUtil.exe list" and then press Enter to list all current models. 4.     Type "AxUtil.exe create /model:CONTOSOAX /layer:Cus" and then press Enter to add the "CONTOSOAX" model. 5.     Type "AxUtil.exe list" and then press Enter to list all current models. Notice that the "CONTOSOAX" model is now listed.
Procedure: Edit a Model Version Number
You can use the/manifest parameter in a command to edit or set various fields in the model. For example, you might want to update the version number of a model after you have imported changes. To update a model version number, follow these steps: 1.     Open Start > All Programs > Accessories > Command Prompt. 2.     Enter the following commands to open the appropriate directory. a.     Type "cd\" and then press Enter. b.     Type "cd\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin" and then press Enter. 3.     Type "AxUtil.exe edit /model:CONTOSOAX /manifest:Version="2.0.0.0" and then press Enter to update the version number of the "CONTOSOAX" model. 4.     Type "AxUtil.exe list" and then press Enter to list all current models. Notice that the "CONTOSOAX" model version number is now 2.0.0.0.
Procedure: Export a Model
To export the "CONTOSOAX" model in the user, follow these steps: 1.     Open Start > All Programs > Accessories > Command Prompt. 2.     Enter the following commands to open the appropriate directory. a.     Type "cd\" and then press Enter. b.     Type "cd\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin" and then press Enter. 3.     Type "AxUtil.exe export /file:c:\CONTOSOAXModel.axmodel /model:CONTOSOAX" and then press Enter to export the "CONTOSOAX" model.

           

Procedure: Delete a Model
To delete the "CONTOSOAX" model, follow these steps: 1.     Open Start > All Programs > Accessories > Command Prompt. 2.     Enter the following commands to open the appropriate directory. a.     Type "cd\" and then press Enter. b.     Type "cd\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin" and then press Enter. 3.     Type "AxUtil.exe delete /model:CONTOSOAX" and then press Enter to delete the "CONTOSOAX" model. 4.     Type "Y" to confirm the deletion. 5.     Type "AxUtil.exe list" and then press Enter to list all current models. Notice that the "CONTOSOAX" model is no longer listed.
Procedure: Manage Label Files
To create a "CONAX" label file, follow these steps: 1.     Open a new development workspace, click the windows icon in the upper-right corner, then New Development Workspace, or press Ctrl+Shift+W. 2.     Open AOT > Label Files. 3.     Right-click Label Files > Create in Label file Wizard. 4.     Select Create new label file ID, then click Next. 5.     In Label file ID, type "CONAX", then click Next. 6.     Click Finish. 7.     Expand Label Files, and note that a "CONAX" label file has been created in the current layer and model.

Microsoft Dynamics AX 2012 Posting Profile Concept

Microsoft Dynamics AX 2012 Posting Profile Concept

The posting profiles are the integration point between the sub module (Fixed assets, Payables, Inventory, Banks, Receivables, Project, and Production)  and general ledger sub module, it is a set of ledger accounts which are used in generated an automatic ledger entry where transaction occurred. We could select different ledger accounts for each type of sub modules transactions.

The application consultant working with the controller in several workshops during the implementation phases, in the analysis phase to identify the business requirements in financial directions, in the design phase to identify the integrations point through the posting profiles for each module, in the deployment phase apply the posting profile in MS Dynamics AX 2012 and get the user acceptance (UAT) by testing every transaction and ensure that MS Dynamics AX 2012 is generate the correct entry based on the posting profile setup.

MS Dynamics AX 2012 master data are designed to be contained a group for categorization from the sub module point of view, for example the customer groups are build up  considering two main sides first side is the customers categorizations for sales reporting (Business domain, Company relations, Customer size, import, and export), and the second side is financial direction, whether setting up the posting profiles based on customer groups where each customer group is mapped into a ledger account.     

MS Dynamics AX offers a great flexibility in posting profiles setups where the posting could be on three different levels as the following:-

All	Any transaction occurred on any customers will be directed to the ledger account which assigned to all customer
Group	Any transaction on a particular customer inherits the posting profile of the customer group to which the customer is assigned.
Table	Any transaction occurred on a particular customer will be directed to the ledger account which is assigned in the posting profile

 The controllers have a common question during the design phase which level of All, Group, and Table is dominate over the other level, and do we can to assign customer to a specific group, but exceptionally this customer should be directed to another ledger account.

The logic of posting profile domination in MS Dynamics AX 2012 is working as the following, the lowest level is Table where specify customer ID is dominate over Group, and All.

For example: All customers directed to same ledger account, except one group is directed to another ledger account, exceptionally one customer directed to a third ledger account.

- See more at: http://blog.mohamedaamer.com/microsoft-dynamics/ms-dynamics-ax-2012-posting-profile-concept/#sthash.EF80kujX.dpuf

Error System.Security.Permissions.EnvironmentPermission while running report

Error System.Security.Permissions.EnvironmentPermission while running report: 

Microsoft Dynamics AX 2012 Reporting extensions

We run into issue that whenever we used a Microsoft Dynamics AX configuration file with a Reporting Services instance (as mentioned in here: http://technet.microsoft.com/en-us/library/hh389774.aspx) the following error was reported the first time a report was run after the restart of the SQL Reporting Services instance:

"The DefaultValue expression for the report parameter ‘AX_CompanyName’ contains an error: Request for the permission of type 'System.Security.Permissions.EnvironmentPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. (rsRuntimeErrorInExpression)"

Running the report for the second time, it renders without any error. The error is mostly seen with subsequent instances of Reporting Services because only then an Microsoft Dynamics AX configuration file (Microsoft.Dynamics.AX.ReportConfiguration.axc) is used but any Reporting Services instance that is set up to use an AX configuration file will throw this error.

The resolution we found was to use "FullTrust" permission set in place of  "Execute" for the "Report_Expressions_Default_Permissions" in the rssrvpolicy.config

Existing configuration:

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions"
Description="This code group grants default permissions for code in report expressions and Code element. ">

[...]

</CodeGroup>

Replacement configuration:

<CodeGroup
class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="Report_Expressions_Default_Permissions"
Description="This code group grants default permissions for code in report expressions and Code element. ">

[..]

</CodeGroup>

AX 2012 Hands on Labs

AX 2012 Hands on Labs

There are a number of guided Hands on Labs now available on Partner Source, they can be found following the links below: 

1. Workflow Implementation
2. Accounts Payable
3. Accounts Receivable Enhancements
4. Expense Management
5. Migrating Reports to SSRS
6. Employee Procurement
7. Client Forms
8. Export Extend and Refresh
9. Edit Budgets in Excel
10. Sales Quotations in Word
11. Import Data Using Excel
12. Project Accounting

Read the complete post at http://blogs.msdn.com/b/ukax/archive/2011/04/15/dynamics-ax-2012-hands-on-labs.aspx

Understanding Opportunities in AX2009 – CRM Module

Understanding Opportunities in AX2009 – CRM Module

One of the nice upgrades in AX 2009 is the addition of Opportunities in the CRM module.  During a recent AX2009 -CRM module training event, it became clear that the term “Opportunities” doesn’t always fit nicely into the way some organizations think about their CRM process.  Here’s a quick overview of Opportunities and how they fit into AX.

One way to think about Opportunities is your Pre-Sales Bucket.  This bucket contains everything you need to create, develop and close sales deals.  Opportunities pick up where Leads end.  In most organizations it is important for there to be separate definitions for recording and working with potential-sales that are unqualified (Leads), and qualified (Opportunities).  In AX2009, Opportunities keep up with:

·Communications

·Contacts

·Competitors

·Partners

·Products being quoted

·Quoted Prices

·Quantities

·Sales Stage

·Associated documentation

Opportunities are not necessarily companies, and they can contain multiple contacts.  From AX2009:

When your lead record has become an opportunity record, you can start to track more sales-related information such as quotations and competitors. Tracking the competition for the sale can give you valuable information about how to win the opportunity and gain another customer.

When you manage your opportunities, you can also give probability percentages and prognosis ratings to the opportunity and track the probability percentage, or chance that the opportunity will become a customer.

As soon as you have provided quotations and the contact at the opportunity has made a decision, you can track whether you won the opportunity and the reason why you won it. If you have lost the opportunity, you can list why and to whom you lost the opportunity, as this information might be useful later.

The slide below illustrates how Opportunities and Leads fit into the AX2009 – CRM flow: