Pages

Thursday, 18 September 2014

What is sure step methodology in ax 2012

Microsoft Dynamics Sure Step is the prescribed methodology for deploying Microsoft Dynamics AX. The Sure Step application
provides product-specific and general project-based templates, workflows, process maps and tools to assist the implementation partners. Sure Step is currently available as an online tool or for download from Partner Source.

The Sure Step methodology is divided into the following phases:




        Try to observe the above picture and explained below briefly.

Diagnostic
Evaluate a customer's business processes and infrastructure Assist the customer with their due diligence cycle, including
ascertaining requirements and their fit with the solution,and assessing the resource needs for the solution delivery Prepare
the project plan, proposal, and the Statement of Work.

Analysis
Analyze current business model and finalize the Functional Requirements document Finalize the fit-gap analysis Develop
the Environment Specification documentation.

Design
Develop the Functional Design, Technical Design, and Solution Design documents Finalize the data migration design Establish
test criteria.

Development
Finalize configurations and setup of the standard solution Develop and finalize the custom code that is required to support
the solution Conduct functional and feature testing of the solution Create the user training documentation.

Deployment
Set up the production environment Migrate data to the production environment Conduct user acceptance test of the system Train
users and finalize the user documentation Conduct go-live check and promote the system to production.

Operation
Resolve pending issues Finalize user documentation and knowledge transfer Conduct a post-mortem of the project Provide on-going
support (activities that continue through any future involvement with the customer after the project is closed).

The Sure Step methodology also provides guidance for the following areas:

Optimization
Leverage Review Offerings to determine proactively if the system is being designed and delivered optimally to meet the customer’s
requirements Analyze the system to determine how it can be optimized for the best performance based on customer's needs.

Upgrade
Assess the customer's current business processes and solution Document the requirements for new functionality Upgrade the system
to new release—including the addition of new functionality, promotion of existing customization that are required, and elimination
of custom code no longer required.

Monday, 15 September 2014

What is Full text index in ax 2012

A full text index contains location information about each significant word in a string field of a table.
Some queries can use this information to run more efficiently and complete much sooner.
These are queries that search for words that are embedded in the middle of string fields
A regular index on a long string field can help a query complete quickly only if the query
searches for the word that is at the start of the string field.
In X++ SQL this is done with the like keyword and the * wildcard character, such as in the code phrase like "*van*".

What is index in ax 2009 and 2012

There are two types of indexes:
Unique and Non-Unique.
Whether an index is unique is defined by the index's Allow Duplicates property.
When this property is set to No, a unique index is created.
The database uses the unique index to ensure that no duplicate key values occur.
The database prevents you from inserting records with duplicate key values by rejecting the insert
Setting the index's Allow Duplicates property to Yes creates a non-unique index.
These indexes allow you to enter duplicate values for the indexed fields and are used for performance reasons.


Microsoft Dynamics AX requires a unique index on each table
so if there are no indexes on a table or all the indexes are disabled,
a system index is automatically created. The system index is created
on the RecId and DataAreaId fields if the DataAreaId field exists.
Otherwise the system index is created on the RecId field.
You can see system indexes in the database but they aren't visible in the AOT.
If there are indexes on a table but none of them are unique,
 the runtime estimates the average key length of the existing indexes,
chooses the index with the smallest key length and appends the RecId column to create a unique index.

 

Tuesday, 9 September 2014

How to create RDP report in Ax 2012

Layer Configuration In AX 2012


Changing Layer in Dynamics AX 2012:

1.      Click Start, point to Administrative Tools, and then click Microsoft Dynamics AX 2012 Configuration. The Microsoft Dynamics AX Configuration Utility opens.

 
 
 
In the Microsoft Dynamics AX Configuration Utility, click Manage, and then click Create configuration. The Create Configuration window opens
 
 
In the Configuration name field, enter a name for the configuration, and then click OK. The Create Configuration window closes
 
 
On the Developer tab, in the Application object layer to open field, select a new layer from the drop-down list.
 
 
In the Development license code field type the license code and  confirm license field also give the same
 
Click Apply and  Click OK to save the configuration. The Microsoft Dynamics AX Configuration Utility window closes.
Close and restart the client in the new layer.
Thanku

 
 

Wednesday, 3 September 2014

How to debug Code in Visual Studio in AX 2012

AX 2012 - How to debug Code in Visual Studio
This post basically addresses how to debug code in Visual studio.
Most of code running on AOS runs in CIL environment, so it cannot be debugg in Microsoft Dynamics AX Debugger.
You might have confused/surprised why ax debugger is not opening inspite of  inserting breakpoint at particular place. It means code might be running in CIL and to debug visual studio 2010 is required.

Step1:
Make sure AOS Service runs on account which you logged in. Right click on AOS Service and change log on property to logged in windows credentials.
Log off windows and then re log in. 
        
Step2:
Open visual studio and click on AX Application explorer (Shortcut Ctrl + D)
AOT opens and you can browse nodes as you used to do in Dynamics AX.
Open the object which you want to debug and insert breakpoint.

Step3:
Then in Visual studio, Click on Debug->Attach process

 
As shown in above image, First make sure two check boxes at bottom are marked.
Then only you can find and able to select AX32Serv.exe(AOS)  process and click on attach button.
Note : When you are doing this step 3 for first time it prompts you to Restart Visual studio, kindly select the same option.
 

Step4:    You done with setting up visual studio to debug code running in CIL.
Now restrart process in Dynamics AX which you want to debugg and you can find Visual studio debugger opened for you.
Continue debugging with hotkeys as you use to do in AX debugger like F10/F11.