Afsar's Dynamics AX knowledge arena

Create a public Enterprise Portal site

2012-01-13T23:56:00.000+05:00

Happy New Year 2012 !!!!!

Due to my busy schedule here in USA, I was unable to share any new post with you guys.
But here is the very nice artical about How to create/expose enterprise portal site publically.
http://technet.microsoft.com/en-us/library/hh285823.aspx

White paper of UK CIS new functionality on Dynamics AX 2012 is available

2011-11-27T23:38:00.002+05:00

I developed a feature for Dynamics AX 2012 named UK Construction Industry Scheme UK CIS has been released in Dynamics AX 2012 CU3 and documentation is available under the following link:

Download Center: http://www.microsoft.com/download/en/details.aspx?id=28155
CustomerSource: https://mbs.microsoft.com/customersource/documentation/whitepapers/ax2012_cu3_unitedkingdom_wp
PartnerSource:https://mbs.microsoft.com/partnersource/deployment/documentation/whitepapers/ax2012_cu3_unitedkingdom_wp

What type of companies can use Dynamics AX 2012

2011-11-21T15:42:00.000+05:00

Customers with 500 to 5000 employees in Public Sector, Manufacturing and Retail industries only
Customers with over 5000 employees
Customers with between 200 and 7500 employees in all industries. The solution includes out-of the box capabilities for Manufacturing, Construction, Retail, Services, and Public Sector industries.
Customers with between 200 and 7500 employees in all industries except Public Sector

Dynamics AX 2012 Cumulative Update 2 is released

2011-11-21T12:59:00.001+05:00

Last week Microsoft announced the Cumulative update 2 for Dynamics AX 2012. Please review the Support KB Article for more details. This cumulative update include

Cumulative Update 1 for Microsoft Dynamics AX 2012.
Translations in 29 languages for labels introduced since RTM. For customers wishing to install a Wave II language they will still require the Wave II Language Pack.
2 country specific updates.
114+ hotfixes released on AX 2012 RTM since Cumulative Update 1 for Dynamics AX 2012.

For more details on fixes included please review the Support KB Article.

Debugging in Dynamics AX 2012 as a non-admin Role

2011-11-11T19:12:00.003+05:00

To access breakpoints as a limited user:
1. open dynamics as admin
2. add yourself to your favorite role (in addition to admin)
3. shift control w to open a workspace.
4. insert a break point into a well know x++ class that the role accesses.
5. create a new job
6. insert this:
static void NonAdmin(Args _args)
{

securityutil::sysadminmode(false);
}
7. run job
8. control w to open regular workspace (or open it from the menus, sometimes its sticky)
9. Open the form/class via navigation

observe that you can now stop in debugger as "limited" user

Microsoft Dynamics Sure Step 2012 Launched

2011-11-09T02:11:00.000+05:00

Microsoft Dynamics Sure step 2012 is officially launched, please read the following article for more details:

Microsoft Dynamics Sure Step 2012

Dynamics AX 2012 Design Patterns

2011-10-19T17:28:00.004+05:00

Following are the design pattern for Dynamics AX 2012 development and smart customizations:

Instantiating Application Objects Design Pattern

Searching for Records Design Pattern
static find Method Design Pattern
static exist Method Design Pattern
Parameter System Design Pattern
Multiselection Design Pattern
Searching for Multiple Occurrences Design Pattern
Change Company Design Pattern
Partner Hooks Design Pattern
Pack-Unpack Design Pattern
Use the Type System Design Pattern
Storno Design Pattern
Persistent Data Storage Design Pattern
Data Validation Design Pattern

Set focus on specific control when opening form

2011-10-17T16:32:00.001+05:00

To set the focus on specific control when form is open, you need to override the firstField() method of the form and set your desired control after super() call.

public void firstField(int _flags=1)

{
    ;
    super(_flags);
    desiredControlName.setFocus();
}

Dynamics AX 2012 SSRS reports patterns

2011-10-17T15:18:00.002+05:00

Here are the design pattern/changes that we need to make sure for AX 2012 SSRS report development:

Functional Area	AX2009	AX2012
Input parameters (definition)	Report	Data contract (*)
Input parameters (validation)	Report	Data contract (*)
Input dialog (simple)	Report	Data contract (*)
Input dialog (complex)	Report	UI Builder (*)
Input parameters (modification)	Report	Controller (*)
Dynamic query	Report	Query
Report data	Report	Table (temp)
Business logic	Report	RDP
Report layout	Report	SSRS Report

Dynamics AX 2009 and Dynamics AX 2012 modules comparisons

2011-10-17T00:22:00.000+05:00

Following are the enhancements made by Microsoft on Dynamics AX 2012:

For example, GL module in AX 2009 is now break into GL and Fixed assets in AX 2012.

AX 2009 Module	AX 2012 Module
General Ledger	General Ledger
	Fixed Assets (New)
Bank	Cash and bank management
Accounts Payable	Accounts Payable
	Procurement and sourcing (New)
Accounts Receivables	Accounts Receivables
	Sales and Marketing (New)
Inventory Management	Product information (New)
	Inventory and warehouse management
Expense management	Travel and expense management
Production	Production control
Project	Project management and accounting
	Compliance and internal control (New)

Change company logo on EP home page

2011-09-24T23:43:00.000+05:00

Here is the very useful link for displaying/changing the Dynamics AX 2009 EP home page.
Display Company Logo on Dynamics EP Site and Hide Page Title

alternatively/in dynamics ax 2012, you can change the logo from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ep\images\ location and change the name you your logo file to DynamicsLogo64x64.png

Cannot connect to the Configuration database error – SharePoint 2010

2011-08-24T10:55:00.003+05:00

Resolution steps:
1. If the WSS is in a server farm, use the “SharePoint Products and Technologies Configuration Wizard” to disconnect the server from the farm.
2. Navigate to Start >Program > Microsoft SQL Server 2005 > Configuration Tools >SQL Server Configuration Manager
3. Navigate to SQL Server 2005 Network Configuration > Protocol for MSSQLSERVER
4. Right click Named Pipes and select Enable (if not enabled)
5. Restart SQL Server
6. Join back the server to server farm using “SharePoint Products and Technologies Configuration Wizard” and follow the wizards
Note: If the installation is a stand-alone installation, then you don’t need to worry about steps 1 & 6

Show/Hide the dialog range field

2011-08-24T01:00:00.001+05:00

To hide/show the query dialog field, you need to implement/override the showIndexFields() method of the dialog and return FALSE if you want to hide the field from the dialog query range.

here is an example:

public boolean showIndexFields(tableId _tableId)
{
boolean ret = true;

switch (_tableId)
{
case tableNum(YourTable):
ret = false;
break;
}

return ret;
}

Dynamics AX 2012 Price list

2011-08-24T00:54:00.001+05:00

If you are interested in knowing the cost of a Dynamics AX 2012 license, Microsoft has provided a an Excel sheet that can help you estimate the cost of your implementation.

You can download the sheet from here

Drum Roll Please… Microsoft Dynamics AX 2012 is now on the market!

2011-08-01T23:52:00.001+05:00

Dynamics AX 2012 is released on 25 countries, please see the details:
Dynamics AX 2012 released !!!!

MS Dynamics AX 2009 EP development

2011-07-26T22:32:00.000+05:00

To start working on Dynamics AX 2009 EP, the following article will help you a lot:

Dynamics AX 2009 EP Development

Dynamics AX technical consultant interview questions

2011-07-25T00:16:00.000+05:00

I am going to share some frequent interview questions that generally asked for Dynamics AX Technical consultant position:

How can we create primary key for a table?
what precautions you need for overriding fetch() method for a report?
Difference between OCC and PCC?
How many types of MAP there in Dynamics AX?
What is cache lookup what is it used for?
Difference between table and views?
why we use dialog? and how to accomplished it?
what are the different type of index?
Difference b/w cascade + restricted and restricted delete actions?
In which case delete_from and delete() have same result?
Explain sales/purchase order processes in AX.

I will share more questions in my next post.

Dynamics AX 2012 White papers are now available

2011-07-13T12:44:00.001+05:00

Dynamics AX 2012 white papers are now available for download:
Dynamics AX 2012 white papers

We have done it, We proud to be the part of Dynamics AX 2012 development and now its ready for City of Redmond

2011-06-25T01:02:00.000+05:00

As My company own the public sector solution for the Dynamics AX 2012 release and I am glad to see the implementation of Microsoft Dynamics AX 2012 for the City of Redmond USA, see this case study:
Microsoft Case Study: Microsoft Dynamics AX 2012 - City of Redmond

Upgrade Dynamics AX 4.0/AX 2009 to Dynamics AX 2012

2011-06-22T20:16:00.001+05:00

Setup source Environment

1. Import the PreProcessing (databaseupgrade\xpo\UpgradeAX5.xpo) XPO, located in the installation CD folder and Un check "Import with ID values:"

2. Open the PreProcessing Checklist "SysCheckList_PreUpgrade50" located in the AX50PreUpgradeFramework project.

3. The Preprocessing Checklist appears, if your checklists has this @ABC123 instead of text, and then do this to get the missing label file. To apply the new label files in your AX4/5 machine (if you are working with preprocessing framework):

· Copy the label file to the label folder in your AX4/2009 machine

· Restart the AOS

· Label folder in AX4/2009 is a sub folder under ...\Application\Appl\ where you can find *.ald files in it.

4. Run through the PreProcessing Checklist Items to prepare the database for Upgrade

· If upgrading AX 2009, and the upgrade scripts don't run after opening the cockpit, jump to step #12 and follow the steps there to setup the batch server (AX4 does not require setting up a batch server). Then come back to this point and continue.

· If upgrading AX4, You need to compile the ReleaseUpdate* classes and the ReleaseUpdateCockpit form.

· If upgrading AX4, when running the cockpit run multiple instances of AX4:

o Start the new Microsoft Dynamics AX client.

o Select Basic > Periodic > Batch > Processing.

o A batch dialog appears.

o Add DataUpgrade in the Group field, and click OK.

5. In the Inventory Dimension Group Upgrade checklist Item, click on the “Map dimension groups 1:1” button (Do not click on the “Assign identical groups” button) and then click on the “Set to Ready For Upgrade” button.

6. In the System Parameters checklist Item, select “en-us” as the default language and click on the “Set to Ready for Upgrade” button.

7. In the Company Priority setup, click on the “Set to Ready for Upgrade” button.

8. In the Product Upgrade Form, click on the Synchronize button and then on the Product Mapping -> Map all items 1:1. Click on the “Set to Ready for Upgrade” button after doing these steps.

9. In the Units form, click on the “Automatically assignment” button.

a. Set all decimals to 2

b. Set all Unit classes to “Length”

c. Click on the “Validate” button to make sure no errors are found

d. Click on the “Set to Ready for Upgrade” button.

10. In the Pre-Upgrade of Unit Conversions checklist item click on the Validate button and then on the “Set to Ready for Upgrade” button.

11. In the Pre-Upgrade of Unit Texts click on the Validate button and then on the “Set to Ready for Upgrade” button.

12. In the Pre-Upgrade Data checklist item you might need to configure the Batch Server and Batch Server Groups if the Live PreProcessing scripts don’t start running. In order to do so, go to Administration\Setup\Server Configuration

13. Make sure that only the machine you are using has the Is Batch Server checkbox checked. Now go to the Batch Server Groups tab and select the DataUpdate Batch Server Group

14. Another configuration that is required to start running these jobs is the Batch Group form. You can access this in Administration\Setup\Batch Groups

15. Select the DataUpdate Batch Group and go to the Batch Servers tab.

16. Make sure the machine you’re running the upgrade on is on the Selected Servers list on the left side pane.

17. After running the Live PreUpgrade, continue with the next checklist items (Validate Pre Upgrade, check Single User Mode and Single User Mode Upgrade)

18. Once the checklist is finished, the PreProcessing stage is done. Uninstall AX50 (don’t drop the database) and you are ready to go to the AX6 steps.

Starting an Upgrade from the Target Environment

1. Install Dynamics AX 2012.

2. Setup Ax 2012 pointing the AOS to a new Database . Specify a different database name for the Model Database. Make sure you select the "Register Database for Upgrade checkbox:"

3. At this stage, you should have 3 databases in your system: Database

· The AX50 PreProcessed database

· The new AX6 database

· The new AX2012 model database

4. Start AX 2012 and run through the Upgrade checklist

5. In the Provide License Information step, specify the license.

6. At this point, the Target Environment upgrade process is started. Make your way through the first five checklist items.

Data Upgrade Stages

Source DB connection step:

In the Source DB connection step, specify the server name where the Source Database is located and the Source Database name. Click OK once this information is entered.

PreSynchronize step:

This step loads the Upgrade cockpit. Depending on which stage you started the Upgrade Process; you might need to configure the Batch Groups and Batch Servers. Once this configuration is set, click the Run button. PreSync scripts should start running at this stage.

Create Tables Step:

This step synchronizes the database. No special steps need to be taken here.

Generate table and field mapping:

This step generates table and field mapping between source and target systems. There should be no mapping with error.

Generate Bulk Copy and Script Prioritization Step:

Bulk Copy Priorities and Script-Table dependencies are resolved in this step. No special steps need to be taken here.

Launch Data Upgrade Step:

This step loads the Upgrade cockpit. Once the cockpit is loaded, click on the Run button and the Post Sync scripts should start running.

This is where the data is actually copied from the Source Database to the Target Database based on the Mappings found in the Generate Table and Field Mapping step.

Install Dynamics AX 2009 Reporting Extensions with SQL server 2008

2011-06-21T00:18:00.000+05:00

Sometime back, I have experience on interesting issue while installing Reporting Extensions with SQL server 2008, When I run the Setup, I get the following message : "You must install SQL server 2005 Reporting Services Service Pack 2 before installing the report extensions". Here is the workaround

1. Locate the Dynamics AX 2009 Reporting services dll from the extracted AX 2009 SP1 folder[\\AX2009SP1\support\axsetupresources\microsoft.dynamics.setup.reportingservices.dll;File Version - 5.0.1000.52]
Extract the AX 2009 .iso to a folder
Copy the microsoft.dynamics.setup.reportingservices.dll into the folder: \\DynamicsAX\Msi\Components32\Program Files\Microsoft Dynamics AX\50 and Setup\\DynamicsAX\Msi\Components64\Program Files\Microsoft Dynamics AX\50\Setup
It will ask to replace the existing dll having File Version - 5.0.593.0. Say Yes and replace.
5. Then Install AX Reporting Services extensions. It works fine and the Reporting Extensions are installed nice.

Dynamics AX 2012 Programming model

2011-06-20T13:03:00.003+05:00

The following table lists which programming model or models are best used in each development pattern.

<> <>

Design Pattern		Programming Model
	Strongly typed .NET interop to X++	Services	Object-oriented development in X++
Customization	Use to access functionality implemented in X++ from .NET. Where appropriate, you should use eventing to decouple customization business logic implemented in .NET.	Not recommended	Layer-based X++ source code customization is supported. Where appropriate, you should use eventing to decouple customization business logic implemented in X++.
Integration	Not recommended	Use service interfaces to access Microsoft Dynamics AX.	Not recommended
External application development	Use if your Windows application runs only on the AOS server.	Use service interfaces to access Microsoft Dynamics AX in all other cases, including applications that are not Windows-based.	Not recommended
Report development	Not recommended	Use service interfaces when implementing data methods as your report data source type.	Use when developing an RDP data source type for your reports
Enterprise Portal application development	Use from Enterprise Portal applications to access business logic that is in X++ classes.	Use services to access Microsoft Dynamics AX functionality, especially if the application is Internet facing.	Not recommended

Dynamics AX 2012 Step By Step Installation

2011-06-09T15:00:00.000+05:00

Dynamics AX 2012 Step By Step Installation is available on MSDN
AX 2012 Step By Step Installation

How to Debug batch jobs and service operations in Dynamics AX 2012

2011-05-30T16:25:00.002+05:00

All batch jobs and service operations now run in managed code (IL) and require different debugging steps. Rather than setting breakpoints within X++, you need to set them within the IL code that corresponds to the X++ code and debug in Visual Studio.

Open Visual Studio as 'administrator' and attach the debugger to the Ax32Serv.exe process.
Note that it may also be necessary to change the ‘Attach to’ selection to ‘Managed (v4.0) code’ and make sure “just my code” is unchecked in VS: tools->options->debugging->General
Once done, open up the file you want to debug in Visual Studio. All of the X++ code is compiled into IL and can be found in the following directory after deployment: ..\Program Files\Microsoft Dynamics Ax\6.0\Server\AxaptaDev\Bin\XppIL\source\
Set a breakpoint in the file you opened.
Go to Ax and run the process in batch mode, or execute the service operation. This will end up hitting your breakpoint, provided you set it in the right place.

If you make some changes to X++ code and want those changes reflected in the generated IL code, you need to do the following AFTER you have compiled the X++ code.Once done, your changes will be reflected in your next debugging session:

Dynamics AX 2012 AXUtil.exe command-line utility for models

2011-05-30T16:11:00.003+05:00

A new command-line utility, called axutil.exe is used to work with models and model files. You can use this utility to create, export, import, uninstall, and list installed models. You can use the axutil.exe Help for an overview of various commands and parameters used by each command. The setup program uses this utility to install the Microsoft Dynamics AX 2012 application.

Breakpoints in forms button click() method is now operational in Dynamics AX 2012

2011-05-30T16:09:00.001+05:00

Great news for the developers, the pain point on Dynamics AX 2009 related to the unavailability of breakpoint in form's button click() method is no longer exist in Dynamics AX 2012. User can insert breakpoint in from's button click method as he can do it in other locations. Traditionally user write 'breakpoint' to debug the code on form's click() method.

Dynamics Ax 2012 - accessing the correct QueryBuildDataSource for a FormDataSource

2011-05-30T15:55:00.002+05:00

Traditionally within Forms it has been rather cumbersome to get to the QueryBuildDataSource for a specific FormDataSource within Forms. You had to write code such as this:

public void FormDataSource::init()
{
    QueryBuildDataSource qbds;
    super();
    qbds = this.query().dataSourceTable(tableNum(CustTable));
}

That’s all fine and dandy if you have a simple Form, but on some Forms you might have multiple instances of CustTable, especially with the advent of ReferenceDataSources. In these cases you might fall back to using the name of the FormDataSource to ensure you get the correct QueryBuildDataSource:

public void FormDataSource::init()
{
    QueryBuildDataSource qbds;
    super();
    qbds = this.query().dataSourceName(this.name());
}

This is also problematic in the cases that a different query is applied to the Form, such as in the CopyCallerQuery from a List Page to a Details Page. This makes it all very confusing and difficult, and to tell you the truth, we have a very long method in the kernel that finds the correct QueryBuildDataSource for the respective FormDataSource. The good news is those methods are now exposed to X++!
With Dynamics AX 2012 you can now use the methods “FormDataSource::queryBuildDataSource()” and “FormDataSource::queryRunQueryBuildDataSource()”. The first method will return you the QueryBuildDataSource in the FormDataSource.query(), while the second will return you the QueryBuildDataSource in the FormDataSource.queryRun().query(). There’ll be another blog entry discussing when using each is appropriate, but the short of it is use the first whenever you want to modify the QueryBuildDataSource and have the modification stay throughout the life of the Form (such as adding developer ranges that you never want the user to be able to change). The second should be used when you want to make modifications that will just live for the current “executeQuery” call and will be cleared whenever the user clicks on the “Clear Filters” button.
Want to see any additional APIs? Let us know and we can consider adding them.

Non admin debugging in Dynamics AX 2012

2011-05-30T15:52:00.004+05:00

1.) Add the admin to the roles that you want to test. Note that it is ok to leave the admin user in the system administration role.
2.) Open a dev workspace and close the application work spaces.
3.) Set applicable breakpoints.
4.) Create a job with the following line of code and execute: SecurityUtil::sysAdminMode(false);
5.) So at this point the current session is in “non-admin mode”.
6.) Use Ctrl+W to open the application work space. You should notice that few menus / menu items are available
7.) Run the test and any break points set will be hit.

Current constraints / limitations

When SecurityUtil::sysAdminMode(…) is invoked, it is only applicable to the current session. So you must use CTRL+W to open the app workspace; launching a new client will not work.
Since this is scoped to the current session scenarios like run-as are not supported and also services / EP is not supported at this point.

Trade and Logistics training

2011-05-30T12:34:00.000+05:00

Such a great side for SCM learning:
Dynamics AX training

Microsoft Dynamics AX 2012 Beta

2011-04-18T03:38:00.002+05:00

Here is the list of tools and resources available for developers working with the Dynamics AX 2012 Beta:

Getting Started with the Beta

	Download the Beta VM from PartnerSource! (requires valid PartnerSource login)
	Download the Beta VM from CustomerSource! (requires valid CustomerSource login)
	Go to the Developer Help on MSDN
	Read About What's New for Developers on MSDN
	Download the Document What's New for Developers in Microsoft Dynamics AX 2012

courtesy by MSDN

Dynamics AX 2012 Hands on Labs

2011-04-18T03:29:00.002+05:00

Here is the list of new enhancement made on Dynamics AX 2012 release:

Thats it !!!!!!!!!!!!!!!!!!

Creating transfer order through X++ code

2011-04-15T11:51:00.001+05:00

To create a transfer oder via a code:

inventTransferTable.clear();
inventTransferTable.initValue();
numberSequenceReference = InventParameters::numRefTransferId();
numberSeq =
numberSeq::newGetNumFromCode(numberSequenceReference.NumberSequence);
inventTransferTable.TransferId = numberSeq.num();
inventTransferTable.InventLocationIdFrom = fromloc;
inventTransferTable.modifiedField(fieldNum(InventTransferTable,InventLocationIdFrom));
inventTransferTable.InventLocationIdTo = toloc;
inventTransferTable.modifiedField(fieldNum(InventTransferTable,InventLocationIdTo));
inventTransferTable.TransferStatus = InventTransferStatus::Created;
inventTransferTable.insert();

inventTransferLine.clear();
inventTransferLine.initFromInventTransferTable(inventTransferTable,
NoYes::Yes);
nventTransferLine.ItemId = item;
inventTransferLine.initFromInventTable(InventTable::find(item));
inventTransferLine.QtyTransfer = qty_ship;
inventTransferLine.QtyShipNow = 0;
inventTransferLine.QtyReceiveNow = 0;
inventTransferLine.insert();

Also set the two fields:

QtyRemainShip and QtyRemainReceive to the value of QtyTransfer when you create the line.

Dynamics AX 2012 Developer papers is now available on MSDN

2011-04-11T15:47:00.000+05:00

The developer documentation for Dynamics AX 2012 is now available on MSDN
Microsoft Dynamics AX 2012 Beta

Display all/specific AOT tables in a lookup

2011-04-06T12:53:00.004+05:00

For displaying all/specific AOT objects like tables in the lookup control, we need to iterate the UtilidElements table with our desired criteria.

static void lookupAOTTables(FormStringControl _ctrl)
{
   SysTableLookup sysTableLookup =
    SysTableLookup::newParameters(tablenum(UtilidElements), _ctrl);
   Query query = new Query();
   QueryBuildDataSource queryBuildDataSource;
   QueryBuildRange nameQBR, typeQBR;
   ;
   sysTableLookup.addLookupfield(fieldnum(UtilidElements, Name));
   sysTableLookup.addLookupfield(fieldnum(UtilidElements, Id));

   queryBuildDataSource = query.addDataSource(tablenum
    (UtilidElements));

    nameQBR = queryBuildDataSource.addRange(fieldnum(UtilidElements,
    name));
   nameQBR.value('Cust*');

    typeQBR = queryBuildDataSource.addRange(fieldnum(UtilidElements, recordType));
   typeQBR.value(SysQuery::value(UtilElementType::Table));

    sysTableLookup.parmQuery(query);
   sysTableLookup.performFormLookup();
}

Count total number of records

2011-04-01T00:28:00.000+05:00

To count number of records in a query, you just need check it through SysQuery::countTotal(QueryRun) and if the query have more than one data sources use SysQuery::countLoops(QueryRun) instead of SysQuery::countTotal(QueryRun).

Happy Daxing

Error executing code: The method has been called with an invalid number of parameters

2011-03-15T14:57:00.001+05:00

One of the great features of Dynamics AX is the rich integration with other applications or services. The Dynamics AX client is for example exchanging data with Microsoft Office applications like Microsoft Office Excel or Microsoft Office Outlook. Some of these interactions are performed using COM. When the Dynamics AX Client is using COM for the data exchange in certain situation it can happen you are getting confronted with one of the following error message:

Error executing code: The method has been called with an invalid number of parameters
The number of arguments provided is different from the number of arguments accepted by the method

Certain situations means, that you are not always getting this error message but only sometimes and the error is not reproducible. The chance of getting this error message is higher when you continue to work in other applications while the Dynamics AX client is performing the COM operation.
One reason for running into this issue can be if the Windows Operating System is replacing the Dynamics AX application window by a ghost window.
When Dynamics AX starts a lengthy COM operation, it is not responding to messages sent by the Windows Operating System in time. So Windows supposes Dynamics AX has stopped responding. When this happens the Dynamics AX application window is replaced by a ghost window until Dynamics AX resumes. Window ghosting is a nice feature that allows the user to minimize, move or close the main window even if the application is not responding. You can easily identify a ghost window as it shows (Not responding) in the window title.
Unfortunately the replacement of the Dynamics AX application window by the ghost window can interfere the COM operation and result in the above error message.
Therefore it can be helpful to turn window ghosting for the Dynamics AX Client off:

Locate the Dynamics AX shortcut in the Windows Start Menu
Click with the right mouse button on the shortcut and select Properties
Go to the Compatibility tab
Enable the checkbox Run this program in Compatibility mode for and select Windows XP (Service Pack 2)

Please note:

We have seen this issue most on Windows Vista and Windows Server 2008 but this issue is not limited to those two
Window ghosting is not the only cause of this issue, so you might continue to see the error message even if window ghosting was turned off

But sometime there exists several possibilities resulting in this situation and disabling Window Ghosting has proven as workaround in some of those. By now we have found some other workarounds as well. But so far there is no once for all solution.
Here are the workarounds we know so far...

Workaround 1: Disable Window Ghosting as described in this post.

Workaround 2: Debug the X++ code down to the line that is causing the error. Once identified, insert one line before this statement a call to the yield method of the xInfo class.
Example: infolog.yield();
namespace = outlook.getNamespace(#mapidef);

Workaround 3: Debug the X++ code down to the line that is causing the error. Once identified, place the statement inside a try / catch block. In the catch block simply retry the operation.
Example: int retryCount = 3;
//...
try
{
     namespace = outlook.getNamespace(#mapidef);
}
catch(Exception::Error)
{
     retryCount--;

     if(retryCount > 0)
        retry;
     else
        throw(Exception::Error);
}

Dynamics AX - code to Read/Write data to excel

2011-03-07T19:18:00.001+05:00

Writing Data to Excel file
How it works
1. Use SysExcelApplication class to create excel file.
2. Use SysExcelWorkbooks and SysExcelWorkbook to create a blank workbook(by default 3 worksheets will be available).
3. Use SysExcelWorkSheets to select worksheet for writing data.
4. SysExcelCells to select the cells in the excel for writing the data.
5. SysExcelCell to write the data in the selected cells.
6. Once you done with write operation use SysExcelApplication.visible to open
file.

static void Write2ExcelFile(Args _args)
{
InventTable inventTable;
SysExcelApplication application;
SysExcelWorkbooks workbooks;
SysExcelWorkbook workbook;
SysExcelWorksheets worksheets;
SysExcelWorksheet worksheet;
SysExcelCells cells;
SysExcelCell cell;
int row;
;
application = SysExcelApplication::construct();
workbooks = application.workbooks();
workbook = workbooks.add();
worksheets = workbook.worksheets();
worksheet = worksheets.itemFromNum(1);
cells = worksheet.cells();
cells.range('A:A').numberFormat('@');
cell = cells.item(1,1);
cell.value("Item");
cell = cells.item(1,2);
cell.value("Name");
row = 1;
while select inventTable
{
row++;
cell = cells.item(row, 1);
cell.value(inventTable.ItemId);
cell = cells.item(row, 2);
cell.value(inventTable.ItemName);
}
application.visible(true);
}

Reading Data from Excel File

static void ReadExcel(Args _args)
{
SysExcelApplication application;
SysExcelWorkbooks workbooks;
SysExcelWorkbook workbook;
SysExcelWorksheets worksheets;
SysExcelWorksheet worksheet;
SysExcelCells cells;
COMVariantType type;
int row;
ItemId itemid;
Name name;
FileName filename;
;
application = SysExcelApplication::construct();
workbooks = application.workbooks();
//specify the file path that you want to read
filename = "C:\\item.xls";
try
{
workbooks.open(filename);
}
catch (Exception::Error)
{
throw error("File cannot be opened.");
}
workbook = workbooks.item(1);
worksheets = workbook.worksheets();
worksheet = worksheets.itemFromNum(1);
cells = worksheet.cells();
do
{
row++;
itemId = cells.item(row, 1).value().bStr();
name = cells.item(row, 2).value().bStr();
info(strfmt('%1 - %2', itemId, name));
type = cells.item(row+1, 1).value().variantType();
}
while (type != COMVariantType::VT_EMPTY);
application.quit();
}

Inventory Costing in AX 2009

2011-02-28T14:23:00.002+05:00

Here is a good article related to the inventory costing:
https://community.dynamics.com/product/ax/axtechnical/b/axinthefield/archive/2011/02/02/inventory-costing-in-ax-2009.aspx

Get ready for DAX 2012

2011-02-27T23:36:00.002+05:00

Readability issue on customer/vendor aging report

2011-02-27T23:30:00.001+05:00

Most of the time people ask me one common problem they face on customer/vendor aging report. It’s very annoying for them to view Invoice/Voucher field on this report. MS ship this field as single field instead of separating Invoice and Voucher two fields. However we can enhance the readability of this column by modifying the CustVendBalanceList class. The Invoice/Voucher field is setup in the addTrans() method (line#34), here is the actual piece of code:

tmpAccountSum.Txt = strfmt('%1/%2', _voucher, _invoice);

We can put some blank spaces b/w %1 / %2 to increase the visibility of the records on this report.

Lookup Department Dimension on dialog

2011-02-27T23:18:00.001+05:00

Few days back, I received a requirement to show the Department dimension on the report dialog, there are couple of ways to achieve this functionality, but in my opinion, the easiest way to create a new EDT called DepartmentDimension and make a relations to DepartmentDimension == Dimension.num. And 0 == Dinemsions.DimensionCode; where 0 is the dimension you want to use. Finally add following code in the dialog() method of the class:

dialog.addFieldValue(typeid(DepartmentDimension ) ,departmentDimensionVariable ,"Label - if required","help text - if required");

My blog is now on Microsoft Dynamics AX Community

2011-02-01T11:28:00.000+05:00

I am glad to inform you guys that my blog is on on Microsoft Dynamics AX Community:

https://community.dynamics.com/product/ax/axtechnical/b/mafsarkhan/default.aspx

HaPpY DAXing !!!!!!!!!

Restoring AX Database From One Environment to Another

2011-01-30T01:01:00.000+05:00

When you restore a database from a production environment to a test / dev environment, you should run these scripts to ensure that your database is synchronized with the Application environment and proper object server.
Here are some samples scripts you should run:
Select * from BatchServerGroup
–Update BatchServerGroup set SERVERID = ’01@NewAOS’ where SERVERID = ’02@OldAOS’
Select * from BATCHSERVERCONFIG
–Update BATCHSERVERCONFIG set SERVERID = ’01@NewAOS’ where SERVERID = ’02@OldAOS’
Select * from SYSCLUSTERCONFIG
select * from SYSSERVERCONFIG
–Update SYSSERVERCONFIG set SERVERID = ’01@NewAOS’ where SERVERID = ’02@OldAOS’
Select * from SYSSERVERSESSIONS
–Update SYSSERVERSESSIONS Set AOSID = ’01@NewAOS’, Instance_Name = ’01′ where AOSID = ’02@OldAOS’
Select * from Batch
–Update BATCH set SERVERID = ’01@NewAOS’ where SERVERID = ’02@OldAOS’
select * from SYSCLIENTSESSIONS
–delete SYSCLIENTSESSIONS
Beside these, you should also check the Dynamics database for Enterprise Portal, Analytical Server BI setup and reporting server configuration. This could be done through SQL Server access or trough AX Administration setup.

Backup and restore Dynamics AX application files - made easy

2011-01-30T00:59:00.001+05:00

Here is sample code which can be used to automatically copy Dynamics AX application files to an archive. This step is really important if you want to ensure that you safely backup your Application files.
To restore your application, you should copy the application files from the backup to the proper application directory and then start service and compile all objects in the application.
This is the sample batch file which you can run using Task scheduler or any other similar program.
@echo on
for /f “tokens=1,2,3,4* delims=.:/- ” %%i in (‘date /t’) do (
for /f “skip=1 tokens=1-4 delims=/-,().” %%x in (‘echo.^|date’) do (
set weekday=%%i&set month=%%j&set day=%%k&set year=%%l))
REM stop aos service
net stop “Dynamics AX Object Server 5.0$01-XXXXX”
REM maps to folder where backups are stored
net use z: /d /y
net use z: \\Backup
REM creates folder with day and time stamp
z:
cd \
mkdir %weekday%%month%%day%%year%
REM copies app folder to the backup location
XCOPY “c:\Program Files\Microsoft Dynamics AX\50\Application\Appl*.*” z:\%weekday%%month%%day%%year%\app\ /K /O /Y /F /I /E
REM start aos service
net start “Dynamics AX Object Server 5.0$01-XXXXXX”
You should replace the “Dynamics AX Object Server 5.0$01-XXXXX” with your service name.

MS Dynamics AX 6.0 is officially renamed to MS Dynamics AX 2012

2011-01-19T14:24:00.001+05:00

MS Dynamics AX 6.0 is officially renamed to MS Dynamics AX 2012.
Microsoft Dynamics AX 2012 unveiled

Official Details about Dynamics AX '6' released

2011-01-11T18:02:00.001+05:00

2Here we are, kicking off 2011 with a bang for Microsoft Dynamics AX! Next week in the Microsoft Dynamics AX 2011 Technical Conference, in which the primary focus in on Microsoft Dynamics AX '6'.

To kick things off, Microsoft today did a press release, in which official details about the Microsoft Dynamics AX '6' product was released. A direct link to the Press Release can be found here.: Microsoft Previews Next-Generation ERP

This press release was well covered by both MSDynamicsWorld.com, here: Microsoft Confirms Details of Upcoming Dynamics AX "6" Version, as well as MaryJo Over at ZDNet, on her 'All About Microsoft' blog, found here.: 2011 to be a big year for Microsoft in ERP

Secrets of SysLastValue

2011-01-04T15:45:00.000+05:00

SysLastValue is a kernel-level table that does not show up in the AOT data dictionary. There is however a form called "Usage Data" that can be accessed (check tools / development tools / application objects / usage data). The form itself is called "SysLastValue" (yeah, really) in the AOT. We can use the datasource on the form to right/click and table browse this mysterious table.

SysLastValue stores many different things. The majority of records you will find in there pertain to caching, or "last use" type of data, which will remember the last values you've entered on a dialog, the last printer selection you made for a report, etc. But, which is why we're interested, it will also store any user setup you make on a form, and any and all queries being stored. The field "recordtype" will indicate exactly the type of values stored.

We are interested in type "UserSetup" with the "isKernel" flag set to no, these are the user setups on forms, and the "elementName" field will tell you what form name.
Type "UserSetupQuery" contains the queries saved for a form. You will notice the "designname" contains the form's name, and the "elementname" field contains "f:formname".

Happy new year 2011 - the year of MS Dynamics AX 2011 ERP

2011-01-04T15:43:00.000+05:00

Happy new year.

Bye bye AX 2009, now its a time for AX 2011/AX 6.0

Cleanup cache .auc file

2010-12-22T19:45:00.000+05:00

If you wants to delete the local cache, do following steps:

1. Stop AOS.
2. Delete the .auc file from users\\Appdata\ folder
3. Restart AOS.

Run SalesConfirmation report through code

2010-12-22T14:01:00.001+05:00

Here is an example to print the sales confirmation report through code:

static void printSalesConfirmationReport(Args _args)
{
    Args args;
    ReportRun reportRun;
    SalesFormLetter salesFormLetter;
    PrintJobSettings printJobSettings;
    CustConfirmJour custConfirmJour;
    RecordSortedList list = new RecordSortedList(55);
    SalesTable salesTableUpdate;
    ;

    SELECT firstonly custConfirmJour order by ConfirmID desc
    where custConfirmJour.SalesId ==   salesTable.SalesId ;
    list.ins(custConfirmJour);
    args = new Args(ReportStr(SalesConfirm));
    printJobSettings = new PrintJobSettings();
    printJobSettings.SetTarget(PrintMedium::Screen);
    printJobSettings.suppressScalingMessage(true);

    salesFormLetter = new SalesFormLetter_Confirm(true);
    salesFormLetter.updatePrinterSettingsFormLetter(printJobSettings.packPrintJobSettings());
    args.designName("Standard");
    args.caller(salesFormletter);
    args.parmEnum(PrintCopyOriginal::Original);
    args.parmEnumType(enumnum(PrintCopyOriginal));
    args.object(list);
    reportRun = new ReportRun(args);
    reportRun.setTarget(PrintMedium::Screen);
    reportRun.init();
    reportRun.run();
}

Dynamics AX Business Intelligence

2010-12-08T15:52:00.004+05:00

There is a new blog from Microsoft, focusing specifically on Dynamics AX BI. The blog can be found here.:

Dynamics AX Business Intelligence

AX SSRS Reporting Concepts
ScreenCast - AX SSRS Reporting Concepts on YouTube

Dilemma of delete actions- Restricted/Casecade+Restricted

2010-12-08T00:15:00.001+05:00

To explain the difference b/w Restricted and Cascade+Restricted delete action, consider the following example:
Let's say you have tables CarTable and RentalTable, there is a one-to-many relationship between CarTable and RentalTable. Then if a record in CarTable is deleted and the delete action is:

None: No action on related records in RentalTable.

Cascade: All records in RentalTable related to the record being deleted in CarTable will also be deleted.

Restricted: The user will get a warning saying that the record in the CarTable cannot be deleted because transactions exist in table RentalTable. The user will be unable to delete the record in CarTable if one or more related records exist in the RentalTable.

Cascade + Restricted: This option is used when deleting records through more than two levels. Let's say another table existed that had a cascade delete action against CarTable and the CarTable had a Cascade + Restricted delete action against RentalTable. If the record in the top level table was about to be deleted it would also delete the related records in CarTable. In turn, all the records in RentalTable related to the records being deleted from CarTable would also be deleted (Cascade behaviour). If only a record in CarTable was about to be deleted, the user would get the same message when using the Restricted method (Restricted behaviour).

Update changes to Production/live environment

2010-11-25T15:49:00.001+05:00

Most companies have 3 different Dynamics AX environments:

- Development environment
- Test/Acceptation environment
- Production/live environment.

When a customer wants to have changes to their production/live environment, the describe some kind of document with requirements. A developer will implement the requirements in their Development environment. When he is finished someone has to copy the changes to the test/acceptation environment. The customer will test the changes and when he accepts them, the changes have to be copied to the production environment.

This coping of changed code can be done in 2 ways:

- Xpo file (with label files).
- A var layer files (with label files).

Copy the delivered Xpo or layer and label files to your delivery archive directory. (Note use the delivery date in the folder name).
Create in the archive directory a directory backup.
Stop all batch servers.
Stop all AOS.
Remove all cache files (del/s *.aoc).
Create a database backup and copy this to the archive backup directory.(point 2)
Copy the axVar.aod, axCus.aod and axUsr.aod from your test environment to the archive backup directory and to the “old” directory in your application tree. (So you can do layer compare afterwards).
Copy the label files into your application tree.
Start an AOS with a different name and/or Port number. This new AOS should only be used for administration purpose. The reason for this dedicated AOS is that upgrading AX can conflict to the stability of your environment. The end user can experience the next thing: a.
a. Stack traces on the screen.
b. Missing labels.
c. Lost or corrupted data.
d. An occupied phone line of the Dynamics AX administrator, because everyone is phoning him that he or she can’t do her work.
Import the Xpo file and press the recompile button if errors occur. If the error a stays repeat this step one more time.
Administrator/Periodic/SQL Administrator use check/synchronize to update the data model. Run it a second time in diagnostic mode only, to be sure it was ok.
Administrator/Periodic/Compile application. (Compiling from the AOT will not work when no developers license is used)
Stop the administration AOS.
Start live/production AOS.
Start all Axapta batch servers.

Using while select firstonly to avoid validations in Dynamics Ax

2010-11-24T20:13:00.000+05:00

When you execute a select statement to retrieve a single record most of us right the query first. This is followed by a validation to ensure that the query has returned a record. we make it simpler If we right it the way mentioned below

static void WhileSelectInsteadoFSelect(Args _args)
{
    CustTable custTable;
    ;

    //-----General way---------
    // fetch the record first
    select firstonly forupdate custTable;

    //add an additional validation
    if (custTable.RecId)
    {
         custTable.Memo = 'updated value';
        custTable.update();
    }

    //------Alternate--------------
    //prevents the extra 'if' check
    while select firstonly forupdate custTable
    {
        custTable.Memo = 'updated value';
        custTable.update();
    }

    //can also be used for simple readonly
    while select firstonly custTable
    {
        info(custTable.Memo);
    }
}

Intelligent Data Management Framework For Microsoft Dynamics AX

2010-11-21T01:04:00.000+05:00

From the IDMF page.:

"The Intelligent Data Management Framework for Microsoft Dynamics® AX helps administrators optimize Dynamics AX database layout by providing functionality to manage key database layout techniques, by way of intuitive Archiving and Purging capabilities.

The framework provides the platform for reduction in database size by purging and archiving of transactions records from sets of relating entities, while maintaining the consistency and integrity of production data. The Intelligent Data Management Framework provides customers and partners the ability to identify and discover related entities based on the Microsoft Dynamics AX metadata and to determine the purging or archiving criteria for tables.

The Intelligent Data Management Framework also analyzes the Production database to determine usage patterns and assesses the health of the Microsoft Dynamics AX Application. This Framework is compatible with all supported versions of Dynamics AX. The Intelligent Datat Management Framework for Microsoft Dynamics AX is a benefit of staying enrolled in a Business Ready Enhancement plan."

The following is a direct link to a presentation put on by Tao Wang Principal Development Manager Dynamics AX performance, at the AXUG Summit this year: TEC01 - The New Intelligence Data Management (IDM) Tool

Query - A general approach

2010-10-28T17:08:00.000+05:00

Query:
Query can be seen as a class interface for creating select statements.

Use a query in place of a select statement when the structure of the "select" (query) is not known until run time, or when the user should be able to specify the ranges.
In other situations, use a select statement. Select statements are often easier to read, and they are much more compile-time stable.

Queries are embedded in Forms, Reports and RunBase jobs and should always be used with these application objects, unless there are good reasons not to.

Queries are very flexible. Everything can be specified at run time, but specify as much as possible before run time.

Create queries in the Application Object Tree (AOT) where possible, instead of building them in code.

Use intrinsic functions everywhere possible to enable compile-time checking of code.

The range of a query can be specified under program control by using two different techniques, the normal one and the query range value expression. Both take a string as an argument that is not evaluated until run time. The string must fulfill certain syntax restrictions and be as compile-time stable as possible.

Query Range value:

Always use the SysQuery::value method when you are programmatically assigning an atomic value to a query range.

Always use the SysQuery::range method when you are programmatically assigning a value range to a query range. The range method will supply the needed ".." operators.

Always use the SysQuery::valueEmptyString method when you want to have a range which must have a blank value.

Always use the SysQuery::valueUnlimited method when you want to have a completely open range.

Query Range value Expression:

Only use the query range value expressions if the normal query range values cannot be used.

Be aware that query range value expressions are evaluated only at run time (so they are not checked at compile time).

Because the contents of the Query range value expressions should look like X++, you should be careful to format the different data types correctly. Use the strFmt system function or queryValue/queryRange for this. queryValue and queryRange are methods on the Global class.

Place the expression in a range that is defined on the most relevant of the involved fields.

How to put Ax 2009 machine back to a clean state (remove the usr layer)

2010-10-26T12:13:00.003+05:00

1. Stop the AOS (default service name is AOS50$01 for AX5).

2. Delete the user layer aod file (…\Microsoft Dynamics AX\50\Application\Appl\AXDB_App\axusr.aod) and *.aoi files.

3. Delete the metadata file in client %userprofile%\AppData\*.auc

4. Start the AOS.

5. Run AX client and do a synchronize on the Data Dictionary node on the AOT tree.

Axapta AOS cluster

2010-09-15T18:54:00.001+05:00

Setting up the Axapta Cluster environment

The Axapta Object Server environment offers a load balancing feature - called the Axapta Object Server Cluster. A number of object servers can be assigned to the same Axapta Object Server Cluster. A client is configured to connect to a Cluster. It will then choose the server with the lowest number of on-line users. With this approach the Axapta Object Server Environment can also be made fault tolerant. If an Object Server fails, a client can immediately connect to one of the other servers in the same cluster.

Axapta object server cluster

The Axapta Object Server cluster environment is build to provide load balancing and fall back. An Axapta Object Server can be specified to belong to a specific cluster. If the same cluster name is given for a number of object servers they all belong to the same cluster. A user can be specified to connect to a given cluster.

Suppose a number of servers are set up in the same cluster - named AOSC. They should all use the same application and database, and in other aspects have the same settings. All clients connecting to the AOSC should be specified to search for servers belonging to this cluster; otherwise the load balancing mechanism will not work properly. A client starting up against an Axapta Object Server Cluster will start out by broadcasting an UDP package requesting Axapta Object Servers fulfilling names and IP server masks given in the client settings to respond. It is therefore vital that firewalls allow such packages to pass through. The client will receive answers from all Object Servers with information on object server name and the name of the instance plus the number of clients connected to that instance. The client disregards information from servers not belonging to the requested cluster. The client then chooses one of the instances with the lowest number of clients.

Since a client automatically can choose from all servers in a cluster one or more Object Servers can be down without changing the connection procedures. However performance might suffer severely due to higher load on the fewer servers.

Setting up the server

On the server manager select the server of interest and click settings. In the advanced field write -cluster=. The cluster name can be up to 10 characters long.

Setting up the client

In the configuration tool choose the configuration of interest. In the advanced field write -cluster=. The client setting for connecting to an object server depends on two situations. The first situation being both client and Axapta Object Servers being in the same subnet. The second being client and Axapta Object Servers belong to different subnets.

Recall the settings in the configuration utility for connecting to an object server:

* Axapta Object Server Mask
* Axapta Object Server host names
* Axapta Object Server IP Address masks

When the client and Object Servers belong to the same subnet the above three masks can be left blank.

When the client and Object Servers belong to different subnets the IP Address masks should contain the mask for the subnet the Object Servers belong to. An example could be 192.88.253.255, where the last 255 specifies that the search is done among servers in the subnet 192.88.253.*.

Note: If client at any time receives only service response from Object Servers within the same cluster it will automatically choose the least loaded of these servers without having to specify the cluster name in the

client configuration. This means that if your installation is one single Axapta cluster, there is no need to change the existing configuration with respect to cluster name. Just ensure that all relevant Object Servers are

located by client configurations network setup.

Creating New Inventory Dimension - Storage

2010-08-05T16:31:00.001+05:00

AX has 8 standard inventory dimension here is the classification of these 8 dimensions

Inventory Item Dimensions

Size
Colour
Configuration

Inventory Storage Dimensions

Batch
Serial
Warehouse
Location
Pallet

Below is the list of objects that needs to be created or modified while creating a new inventory storage dimension. Please note that the list is not exhaustive enough but contains most of the objects that needs to be modified. Let us assume the name of the new dimension would be 'Test'
xtended Data Types

Following is the table specifying the EDTs that one may need to create for new storage dimension. Reference EDT section specifies which EDT to look at while creating new EDT.

EDT Name = InventTestId
Label = Test
Extends = SysGroup
Type = String
Reference EDT = InventLocationId

Tables

New table 'InventTest' : Look at the table InventLocation for reference and create a new table InventTest. Do not forget to create the field groups, indexes, properties similar to InventLocation. You can duplicate this table and change the required fields, methods, fields groups, indexes, propeties etc.

Table InventParameters : A new method 'numRefInventTestId' needs to be created. Take method 'numRefInventSerialId' for an example while creating this method.

Table InventDim : You will have to create a new field 'InventTestId'. Add this field to field groups, 'AutoReport', 'InventoryDimensions'. Create a new index 'TestIdx' with this field, Add this field InvenyTesId to index 'DimIdx'. Modify the following methods, take cue from code for other dimensions and add the relevant code. Methods are: 'dim2dimParm', 'dimParm2dim', 'emptyDimField', 'findDim', 'findOrCreate', 'formQueryAddDynaLink', 'isFieldIdItemDim', 'isFieldIdTransferReceiptMergable', 'isFieldIdTransferTransitReceiptMergable'.

Table InventDimParm : Add a new field 'InventTestIdFlag'. Add this field to following field groups: 'AutoReport', 'Fixedview', 'View'.

Table InventSum : Add a new method named 'inventTestId'. Take cues from 'inventSerialId' method in the table.

Table InventSumDateTrans : You will have to create a new field 'InventTestId'. Add this field to field groups, 'AutoReport', 'InventoryDimension'. Modify following methods: 'initFromInventDim', 'inventDim'.

Table InventSumDeltaDim : You will have to create two new fields named 'InventTestId', 'InventTestIdFlag'. Add the 'InventTestId' field to following groups : 'AutoLookup', 'InventDim'. Add 'InventTestIdFlag' field to following groups: 'InventDimFlags'. Modify following methods: 'initFromInventDim', 'initFromInventDimParm', 'initInventDim', 'initInventDimParm'.

Table InterCompanyInventDim : You will have to create a new field 'InventTestId'. Add this field to field groups: 'AutoReport', 'InventoryDimensions', 'TmpInventDimensions'. Add the field to following indexes: 'DimIdx'. Modify following methods: 'fromInventDim', 'toInventDim', 'dim2dimParm', 'dimParm2dim', 'formQueryAddLink'.

Table PBATreeInventDim : You will have to create two new fields named 'InventTestId', 'InventTestIdVar'. Add the 'InventTestId' field to following groups : 'AutoReport', 'AllFields', 'InventoryDimensions'. Add 'InventTestIdVar' field to following field group: 'InventoryDimensions'. Add a new method named 'inventTestId'. Take cues from 'inventSerialId' method in the table.

Macros

Following is the list of macros that may need to be modified

InventDimSelect
InventDimJoin
InventDimGroupAllFields
InventDimExistsJoin

Classes

New class AxInventTest : Run the class AxGenerateAxBC and select the table InventTest. This will create new AxBC class for InventTest table and you will have to resolve some errors.

Class NumberSeqReference_Inventory : The method 'loadModule' has to be modified to create a reference for 'Test'.

Class InventDimRenameValue : Add a method 'newInventTest'. Take cue from method 'newInventSerial' for definition of this new method.

Class InventDimTracking : Modify method 'initFromArgs'. Take an example of any of the inventory dimensions for changes.

Class AxInventDim : Add parm and set methods for InventTestId field. Take example of parmInventSerialId and setInventSerialId. Modify method setTableFields to make a call to setInventTestId method.

AxInventDim_PriceDiscTable : Add method setInventTestId. Take example of setInventSerialId for definition of this method.

Class InventDimFixedClass : Add following methods : 'parmInventTestIdFlag' - Take example from parmInventSerialIdFlag method and 'inventTestIdFlag' - Take example from inventSerialId flag method. Create a macro for InventTestId in ClassDeclaration (look at declarations for other dimensions). Modify method 'fieldId2Idx'.

Class TradeInterCompany : Modify method 'createTmpInventSum'.

Class PBALib : Modify method 'createInventDim'.

Apart from these classes there are many more classes that may need modifications like InventMovement, InventUpd and its child classes. InventOnhand and related classes etc. If you want to know more you can search for keyword 'InventSerial' in the classes node and find out.

Forms

Following new forms need to be created

InventTest : Similar to InventSerial.
InvenTestIdLookup : Similar to InventSerialIdLookup

Check Journal Balance - When you meet a problem of "do not balance", this break point will be very helpful.

2010-07-06T18:15:00.001+05:00

Object:

\Classes\LedgerVoucherObject\updateTotals

Invoke Scenario:

When there is some problem about imbalance, this function will be very helpful to track why it is imbalance.

Operation Instance:

General ledger -> Journals -> General journal -> Create a new line -> Click Line -> add lines for journal -> Click button post -> post.

Explanation of codes:
private void updateTotals(LedgerTrans _ledgerTrans)
{
LedgerTrans ledgerTransTotals;
;
ledgerTransTotals.data(_ledgerTrans);
if (transDateTotals.find(ledgerTransTotals)) //line 13
{

ledgerTransTotals.AmountCur += _ledgerTrans.AmountCur;
ledgerTransTotals.AmountMST += _ledgerTrans.AmountMST; //line 16
ledgerTransTotals.AmountMSTSecond += _ledgerTrans.AmountMSTSecond;
ledgerTransTotals.Qty += _ledgerTrans.Qty;
transDateTotals.ins(ledgerTransTotals, true);

}
else //line 21
{
transDateTotals.ins(ledgerTransTotals);
}
}
“ledgerTransTotals” is used to accumulate all the transactions. If the transaction is the first transaction needs to be checked, it goes into line 13. Otherwise, it goes into line 21. The ledgerTransTotals.AmountMST at line 16 should be 0 when the last transaction has been added, or it will not be posted. And you will receive a infolog “The trasaction on voucher *** do not balance”

Post Journal - Illustrate the structure of LedgerJournalcheckPost\postJournal. It is called by most journals.

2010-07-06T18:08:00.001+05:00

Object: Classes\LedgerJournalCheckPost\postJournal

Invoke Scenario:

Most of the journals (including “General ledger”, “Payment journal”, “Invoice journal”, “Invoice register”, “Invoice approval journal”, etc.) will call this method to deal with the posting staff.

Operation Instance:

General ledger -> Journals -> General journal -> Create a new line -> Click Line -> add lines for journal -> Click button post -> post.

Explanation of codes:

while select ledgerJournalTrans order by Voucher, AccountType, RecId //line 99

where ledgerJournalTrans.JournalNum == ledgerJournalTable.JournalNum

{

……

while (ledgerJournalTrans.AccountNum

ledgerJournalTrans.AmountCurDebit

// line 316
ledgerJournalTrans.AmountCurCredite

{

if (!this.postTrans(……))

……

ledgerJournalTrans = this.ledgerJournalTransOffset(ledgerJournalTrans, // line357

swappedAcToPostTaxedFirst);

……

}

……

}

……

if (interCompanyCompanies.elements() > 0) //line 400

{

interCompanyCompaniesEnumerator = interCompanyCompanies.getEnumerator();

while (interCompanyCompaniesEnumerator.moveNext())
{
if (interCompanyJournalIds.exists(interCompanyCompaniesEnumerator.current()))
{
ok = this.postJournalInterCompany(……);
……
}
}
}
Instance: (General journal Form)

GL -> Journals -> General journals -> lines
Add two lines as following:
Account Debit Credit Offset account

11010 1000 12060(intercompany)

21125 200 40112

Line 99: The while loop contains all the lines created in the journal form. In this instance, the while loop will be execute twice. One is for “11010, Offset 12060”, another is for “21125, Offset 40112”.

Line 316: This while loop will be execute twice at most. One is for the Current line account, another is for the offset account. In the end of this loop line357, the ledgerJournalTrans will be changed to its offset account.

Line 400: The codes within the ‘if’ condition is used to post the legertrans for intercompany. In this instance, the while loop inside the ‘if’ condition will be executed once. Because there is only one intercompany record 12060.

Upgrade from AX3.0, AX4.0 to AX 2009

2010-06-25T20:46:00.007+05:00

The steps below provide a high-level overview of the tasks that you must complete to upgrade from Microsoft Dynamics AX 3.0 to Microsoft Dynamics AX 2009.

Back up your existing database and application files.

Import two .xpo files from the installation media to assist with data upgrade.

UpgradeColumnList.xpo, for 32-bit to 64-bit RecId field conversion.

LeftJustified.xpo, for removing any trailing spaces from fields.

Note: To help improve performance, you can apply the LeftJustified.xpo on the database that you create in step 4 after you’ve used the Microsoft Dynamics AX DB Upgrade Preparation tool but before you start the Microsoft Dynamics AX 2009 AOS.

(Optional) To help improve performance, remove all user data and logs of Microsoft Dynamics AX 3.0. For example, clean up the SysDatabaseLog table.

Create an empty database for Microsoft Dynamics AX 2009 in SQL Server 2005.

(Optional) To help improve performance, set initial data and log file sizes so that they don’t increase while you perform the data upgrade process.

(Optional) To help improve performance, set the recovery model to Simple for the Microsoft Dynamics AX 2009 Database.

Run AXDBUpgrade.exe (The Microsoft Dynamics AX DB Upgrade Preparation tool). Note: To help improve performance, you can run this tool in Multithreaded mode. For example, to run this tool in 10 threads, enter AxDbUpgrade.exe P/10 at a command prompt.

(Optional) Apply the LeftJustify file imported in step 2 to the Microsoft Dynamics AX 2009 database created in step 4.

Back up your Microsoft Dynamics AX database. Your database is ready to be upgraded.
Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select the database that you created in step 4.

Copy your upgraded customized file into the correct application directory.

Start the AOS.

Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.

Complete the steps in the Upgrade checklist to finish upgrading.

The steps below provide a high-level overview of the tasks that you must complete to upgrade from Microsoft Dynamics AX 4.0 to Microsoft Dynamics AX 2009.

Back up your existing database and application files (AX 4.0 database and (*.aod, *.ahd, *.ald, *.add, *.khd files from Dynamics AX 4.0\Application\Appl folder; copy these files from configuration that you wants to be upgrade).

Before you upgrade, you must execute the following SQL script on your AX 4.0 database:

--DIMENSIONCOLLECTION

UPDATE SQLDICTIONARY SET FIELDID=1 WHERE FIELDID=50002 AND TABLEID=2897;

UPDATE SQLDICTIONARY SET FIELDID=2 WHERE FIELDID=50005 AND TABLEID=2897;

UPDATE SQLDICTIONARY SET FIELDID=3 WHERE FIELDID=50007 AND TABLEID=2897;

UPDATE SQLDICTIONARY SET FIELDID=4 WHERE FIELDID=50008 AND TABLEID=2897;

--DIMENSIONHIERARCHYCOMBINATION

UPDATE SQLDICTIONARY SET FIELDID=1 WHERE FIELDID=50002 AND TABLEID=2898;

UPDATE SQLDICTIONARY SET FIELDID=2 WHERE FIELDID=50003 AND TABLEID=2898;

UPDATE SQLDICTIONARY SET FIELDID=3 WHERE FIELDID=50005 AND TABLEID=2898;

UPDATE SQLDICTIONARY SET FIELDID=4 WHERE FIELDID=50006 AND TABLEID=2898;

UPDATE SQLDICTIONARY SET FIELDID=5 WHERE FIELDID=50009 AND TABLEID=2898;

--DIMENSIONSETCOMBINATIONDUP2899

UPDATE SQLDICTIONARY SET FIELDID=1 WHERE FIELDID=50001 AND TABLEID=2899;

UPDATE SQLDICTIONARY SET FIELDID=2 WHERE FIELDID=50002 AND TABLEID=2899;

UPDATE SQLDICTIONARY SET FIELDID=3 WHERE FIELDID=50003 AND TABLEID=2899;

--DIMENSIONSETCOMBINATIONTEMP

UPDATE SQLDICTIONARY SET FIELDID=1 WHERE FIELDID=50001 AND TABLEID=2900;

UPDATE SQLDICTIONARY SET FIELDID=2 WHERE FIELDID=50002 AND TABLEID=2900;

UPDATE SQLDICTIONARY SET FIELDID=3 WHERE FIELDID=50003 AND TABLEID=2900;

UPDATE SQLDICTIONARY SET FIELDID=4 WHERE FIELDID=50004 AND TABLEID=2900;

UPDATE SQLDICTIONARY SET FIELDID=5 WHERE FIELDID=50005 AND TABLEID=2900;

UPDATE SQLDICTIONARY SET FIELDID=6 WHERE FIELDID=50006 AND TABLEID=2900;

--PROVISIONALHIERARCHY

UPDATE SQLDICTIONARY SET FIELDID=1 WHERE FIELDID=50001 AND TABLEID=2901;

UPDATE SQLDICTIONARY SET FIELDID=2 WHERE FIELDID=50002 AND TABLEID=2901;

UPDATE SQLDICTIONARY SET FIELDID=3 WHERE FIELDID=50007 AND TABLEID=2901;

Run the Microsoft Dynamics AX 2009 Setup file from the installation media. During installation, select your existing Microsoft Dynamics AX database (don't start AOS service)

Go to AX instance location that you installed in last step, normally this location is in \Microsoft Dynamics\5.0\Application\Appl\ folder, create new folder named 'Old' and copy SYS and GLS (*.aod, *.ahd, *.ald, *.add, *.khd) files from AX 4.0 backup to this Old folder.

Back to the location \Microsoft Dynamics\5.0\Application\Appl\ and paste all AX 4.0 application files (*.aod, *.ahd, *.ald, *.add, *.khd ) from all layers above the LOS layer ( BUS, VAR, CUS, USR, and respective patch layers) to this location. Delete index file (axapd.aoi - if found) from this directory.

Start the Microsoft Dynamics AX 2009 client. The Upgrade checklist is displayed automatically.

Complete the steps in the Upgrade checklist to finish upgrading.

close* methods on a form

2010-06-22T12:37:00.002+05:00

There are “only” 5 ways to close a form:
1. Close - close the form
2. CloseOK – close the form, and set the OK flag – called by the commandbutton: Ok
3. CloseCancel – close the form, and set the Cancel flag – called by the commandbutton: Cancel
4. CloseSelectRecord – close the lookup form, and set return record
5. CloseSelect – close the lookup form, and set return value

The methods in past-tense are used to determine if or how a form was closed:
6. Closed – The form is no longer open
7. ClosedOK – The form was closed by the user clicking ‘OK’
8. ClosedCancel – The form was closed by the user clicking ‘Cancel’

And canClose() is called before any of the close methods get called.

The New Dynamics AX 2011 X++ Editor

2010-06-07T17:28:00.001+05:00

New features have already been added to the next version of Dynamics AX, Microsoft Dynamics AX 2011.
Some of the new features include:

1. Ability to see lines in code
2.Improved IntelliSense features (all possibilities will appear once you type)
3.Great ability to select words in editor without selecting the line from the beginning
4.More colors
5.Ability to check Labels value without going to the Label Editor
6... and many more.

Generic SysTableLookup Method

2010-05-26T15:41:00.000+05:00

It is often needed to write a custom lookup method and the SysTableLookup class can be useful to create lookups from code. However the following method uses the SysTableLookup in the background but can be called easier.

When using the SysTableLookup class, for most of the simple lookups (1 datasource table) it is alway the same. You need the following :

TableId, LookupControl, LookupFields, ReturnFields, SortFields and sometimes the use of a tmpTable.

Now following method is a generic method to user the SysTableLookup class :


public static void doLookup(TableId             _tableId,
                            Container           _lookupFields,
                            Container           _sortFields,
                            FormStringControl   _control,
                            FieldId             _returnItemFieldNum,
                            Map                 _queryRanges    = null,
                            Boolean             _useTmpTable = false,
                            Common              _tmpBuffer = null
                            )
{
    SysTableLookup          sysTableLookup  = SysTableLookup::newParameters(_tableId, _control);
    Query                   query           = new Query();
    QueryBuildDataSource    qbds;
    int                     i;
    fieldId                 lookupFieldId;
    ;
 
    for(i=1;i <= conlen(_lookupFields);i++)
    {
        lookupFieldId = conPeek(_lookupFields, i);
 
        if(lookupFieldId == _returnItemFieldNum)
            sysTableLookup.addLookupfield(lookupFieldId, true);
        else
            sysTableLookup.addLookupfield(lookupFieldId);
    }
 
    qbds = query.addDataSource(_tableId);
 
    for(i=1;i <= conlen(_sortFields);i++)
    {
        qbds.addSortField(conPeek(_sortFields, i));
    }
 
 
    if(_queryRanges)
    {
        rangeEnumerator = _queryRanges.getEnumerator();
 
        while (rangeEnumerator.moveNext())
        {
            qbds.addRange(rangeEnumerator.currentKey()).value(any2Str(rangeEnumerator.currentValue()));
        }
    }
    if(_useTmpTable)
        sysTableLookup.parmTmpBuffer(_tmpBuffer);
 
    sysTableLookup.parmQuery(query);
    sysTableLookup.performFormLookup();
}

Now when you want to create a lookup you can do it easier by doing the following :


public void lookup()
{
    Container   fieldNums       = [FieldNum(CustTable, AccountNum), FieldNum(CustTable, Name)];
    Container   sortFields      = [FieldNum(CustTable, AccountNum)];
    FieldId     returnFieldId   =  FieldNum(CustTable, AccountNum);
    Map         queryRanges     = new Map(Types::Integer, Types::String);
    ;
    queryRanges.insert(FieldNum(CustTable, AccountNum), '4000');
    LIBSysTableLookup::doLookup(TableNum(CustTable), fieldNums, sortFields, this, returnFieldId, queryRanges);
}

So the only thing you need to do is specify the fields, returnfields and sortfields…

Ans let’s look at the following example : We need a lookup with a temporary table. Then we can do it like this :


Container   fieldNums       = [FieldNum(TmpIdRef, Name), FieldNum(TmpIdRef, HelpTxt)];
    Container   sortFields      = [FieldNum(TmpIdRef, Name)];
    FieldId     returnFieldId   = ConPeek(fieldNums, 1);
    TmpIdRef    tmpTable;
    ;
    tmpTable = LIBDifferenceAction::BuildActionClassList();
 
    LIBSysTableLookup::doLookup(TableNum(TmpIdRef), fieldNums, sortFields, this, returnFieldId, true, tmpTable);

refresh, reread, research, executeQuery - which one to use?

2010-05-26T14:32:00.000+05:00

X++ developers seem to be having a lot of trouble with these 4 datasource methods, no matter how senior they are in AX.

1. Common mistakes
Often, developers call 2 of the mentioned methods in the following order:

formDataSource.refresh()
formDataSource.research()

or

formDataSource.reread()
formDataSource.research()

or

formDataSource.research()
formDataSource.executeQuery()

or

formDataSource.research()
formDataSource.refresh() / formDataSource.reread()

All of these are wrong, or at least partially redundant.
Hopefully, after reading the full post, there will be no questions as to why they are wrong. Leave a comment to this post if one of them is still unclear, and I will try to explain in more detail.

2. Refresh
This method basically refreshes the data displayed in the form controls with whatever is stored in the form cache for that particular datasource record. Calling refresh() method will NOT reread the record from the database. So if changes happened to the record in another process, these will not be shown after executing refresh().

refreshEx
Does a redraw of the grid rows, depending on the optional argment for specifying the number of the record to refresh (and this means the actual row number in the grid, which is less useful for AX devs). Special argument values include -1, which means that all records will be redrawn, and -2, which redraws all marked records and records with displayOptions. Default argument value is -2.
This method should be used sparingly, in cases where multiple rows from the grid are updated, resulting in changes in their displayOptions, as an example. So you should avoid using it as a replacement for refresh(), since they actually have completely different implementations in the kernel.
Also, note, that refreshEx() only redraws the grid, so the controls not in the grid might still contain outdated values. Refresh() updates everything, since this is its intention.

3. Reread
Calling reread() will query the database and re-read the current record contents into the datasource form cache. This will not display the changes on the form until a redraw of the grid contents happens (for example, when you navigate away from the row or re-open the form).
You should not use it to refresh the form data if you have through code added or removed records. For this, you would use a different method described below.

How are these 2 methods commonly used?
Usually, when you change some values in the current record through some code (for example, when the user clicks on a button), and update the database by calling update method on the table buffer, you would want to show the user the changes that happened.
In this case, you would call reread() method to update the datasource form cache with the values from the database (this will not update the screen), and then call refresh() to actually redraw the grid and show the changes to the user.

Clicking buttons with SaveRecord == Yes
Each button has a property SaveRecord, which is by default set to Yes. Whenever you click a button, the changes you have done in the current record are saved to the database. So calling reread will not restore the original record values, as some expect. If that is the user expectation, you as a developer should set the property to No.

4. Research
Calling research() will rerun the existing form query against the database, therefore updating the list with new/removed records as well as updating all existing rows. This will honor any existing filters and sorting on the form, that were set by the user.

Research(true)
The research method starting with AX 2009 accepts an optional boolean argument _retainPosition. If you call research(true), the cursor position in the grid will be preserved after the data has been refreshed. This is an extremely useful addition, which solves most of the problems with cursor positioning (findRecord method is the alternative, but this method is very slow).

5. ExecuteQuery
Calling executeQuery() will also rerun the query and update/add/delete the rows in the grid. The difference in behavior from research is described below.
ExecuteQuery should be used if you have modified the query in your code and need to refresh the form to display the data based on the updated query.

formDataSource.queryRun().query() vs formDataSource.query()
An important thing to mention here is that the form has 2 instances of the query object - one is the original datasource query (stored in formDataSource.query()), and the other is the currently used query with any user filters applied (stored in formDataSource.queryRun().query()).
When the research method is called, a new instance of the queryRun is created, using the formDataSource.queryRun().query() as the basis. Therefore, if the user has set up some filters on the displayed data, those will be preserved.
This is useful, for example, when multiple users work with a certain form, each user has his own filters set up for displaying only relevant data, and rows get inserted into the underlying table externally (for example, through AIF).
Calling executeQuery, on the other hand, will use the original query as the basis, therefore removing any user filters.
This is a distinction that everyone should understand when using research/executeQuery methods in order to prevent possible collisions with the user filters when updating the query.

Getting started with tracing

2010-05-21T12:18:00.000+05:00

Install the trace parser

Set up the server to capture tracing

1. Go to your server configuration in administrative tools.

2. Manage > Create configuration, give it a name, ok

3. Tracing tab:

Check X++ method calls

Check Function calls, Check the 'Sql Statement', 'Bind Variables'

Set number of nested calls to 99

Check Allow client tracing on AOS instance

4. Hit Apply

5. Hit OK

6. Go to your Client configuration in administrative tools.

7. Manage > Create configuration, give it a name, ok

8. Tracing tab:

Check X++ method calls

Check Function calls

Set number of nested calls to 99

9. Hit Apply

10. Hit OK.

11. Restart your AOS.

12. Re-launch your Client configuration screen.

Capture a trace

1. Launch your client as 'Administrator' by righ clicking and perform the action you want to trace once without tracing on (to warm up the caches)

2. In the client config click on "Start tracing"

3. Walk the action you want to trace again.

4. In the Client config click on "Stop tracing".

5. Go to the directory specified at the top of the tracing tab in the server config and sort by modified date. The most recent file should be a .trc file.

Analyze the trace

1. Start the trace parser. If it’s the first time you run it, you’ll be asked a bunch of questions. Be agreeable.

2. File > Import, pick that .trc files you just captured.

3. Start analyzing

I normally first go to the X++/RPC tab and filter by type, totals. Sort by Exclusive RPC calls first, see what’s causing issues. Then sort by inclusive RPC calls and see what’s causing issues. Then Exclusive duration, inclusive duration, etc. General rule of thumb is if you see “your code” in the top couple pages of data for any of those things, you should work to make it better. You can jump to the call stacks causing the calls and stuff. Just look for random ways to make your stuff faster, pull from caches instead of doing round trips, cut down on how many times you’re called, etc. No real science to it, just look for crappy stuff and fix it.

If you want to trace the client it’s the exact same thing, only use the client config instead.

If it doesn’t work

· Make sure you have at least 20 gig of free space on the drive where your log files are located. ETW doesn’t like to run with less than that.

· Make sure you restarted the client or AOS after setting up the tracing options.

· Make sure you wait about 15 seconds after you click “start trace” before you start doing stuff. It takes a couple seconds (usually about 5) before the tracing turns on.

Working with Forms in Dynamics AX

2010-01-23T23:29:00.000+05:00

Following links are really helpful for Axapta form development
Part I
Part II
Part III

RunOn property in Axapta

2009-08-27T11:49:00.001+06:00

The class has a RunOn property that have three values: Client, Called From and Server. Objects created from the class will then live at the location specified.
If you choose Called from, the object will live at the tier where the code creating it (by calling the new constructor) is running.
Classes extending other classes will also inherit the RunOn property. You cannot change it if it is Client or Server. If it is Called from, you can leave it or change it to Client or Server.
But someone may wonder that menu items have their RunOn properties, what will happen if the RunOn property of a given menu item pointing to a class is set to Server, whereas the class's RunOn property is set to Client. The answer is that only if the Class's RunOn property is set to Called From, the objects will be created determined by menu item's RunOn property.
Also there is another situation, the class has static main method which has a RunOn property as well. What will happen if the menu item's RunOn property is set to client, whereas main method has a server modifier. The answer is it will determined by main method's modifier.
Axapta will create the objects according to the prioritized sequence of Class's RunOn property, Class's main method's modifier, menu item's RunOn property. And please notice that in Fat Client mode, even you can set the Class's RunOn property to Server, Axapta will still create the objects in client side instead of Server side.

Create and Post Free Text Invoice in AX

2009-08-05T17:39:00.000+06:00

Here is a sample class which is called via Dialog framework to create & post free text invoice using X++ code.

Job:
public void freeTextInvoicePostTestJob()
{
Dialog dialog;
DialogField dlgCustAcc;
DialogGroup dialogPeriodLengthGroup, dialogPeriodLengthGroup1;
DialogField dlgLedgerAcc;

dialog = new Dialog("Free-Text Invoice");
dialogPeriodLengthGroup1 = dialog.addGroup('Cust Table');
dlgCustAcc = dialog.addField(extendedTypeStr(CustAccount));
dialogPeriodLengthGroup = dialog.addGroup('Ledger Table');
dlgLedgerAcc = dialog.addField(extendedTypeStr(LedgerAccount));

if(dialog.run())
{
if(dlgCustAcc.value() && dlgLedgerAcc.value() != '')
FreeTxtInvoiceCreatePost::main(dlgCustAcc.value(), dlgLedgerAcc.value());
else
throw error(strfmt("Either CustAccount or LedgerAccount info is missing."));
}
}

class FreeTxtInvoiceCreatePost
{
}
static void main(CustAccount _custAccount, LedgerAccount _ledgerAccount)
{
CustInvoiceTable custInvoiceTable;
CustInvoiceLine custInvoiceLine;
CustTable custTable;
LedgerTable ledgerTable;
CustPostInvoice custPostInvoice;
LineNum lineNum;
int i;

ttsbegin;
custTable = CustTable::find(_custAccount);
custInvoiceTable.initFromCustTable(custTable);
custInvoiceTable.insert();
ttscommit;

for(i=1; i<=100; i++)
{
ttsbegin;
ledgerTable = LedgerTable::find(_ledgerAccount);
custInvoiceLine.clear();
custInvoiceLine.initValue();
custInvoiceLine.LedgerAccount = ledgerTable.AccountNum;
custInvoiceLine.initFromCustInvoiceTable(custInvoiceTable);
custInvoiceLine.AmountCur = 10.00;
custInvoiceLine.Description = 'FreeTxIv' + int2str(i);
custInvoiceLine.TaxItemGroup = 'full';
custInvoiceLine.ParentRecId = custInvoiceTable.RecId;

lineNum += 1;
custInvoiceLine.LineNum = lineNum;
custInvoiceLine.insert();
ttscommit;
}

custPostInvoice = new CustPostInvoice(custInvoiceTable);
custPostInvoice.run();
}

Updating records and calling super

2009-08-05T11:44:00.001+06:00

Before a record in AX gets updated an external application gets started. This external application is able to do additional update on the same record in AX by using AIF. As the performance of the external route is slow, an additional check is needed to start this process only if needed.

So what do we have?

A. Do I need to compare this with this.orig() before or after super?
B. Do I need to call this external application before or after super?

If we call the external application before super, AX will complain that another user has updated the record. So we have to do it after super. Fine, but what happens…. After super the original record gets equal to the current record. Ouch so the difference between the record and the original record only exists before super. The solution is to make a local buffer variable in the update method that references the original record before calling super. This buffer will still be used after calling super.

Example:

void update()
{
CustTable ctBuffer = this.orig();
Super();
If(this.name != ctBuffer.name)
//call external application
}

AX 2009 TraceParser

2009-08-04T19:51:00.001+06:00

This is very useful link that give some in depths about TraceParser
1. TraceParser Video Training Part I: Installation.
2. TraceParser Video Training Part II: Configuration, Collection and Importing.

Where do you want your code to run today

2009-08-03T16:14:00.000+06:00

Much of the X++ code you write can run on either the Application Object Server, or the Client. The client can be the Win32 client, or BC.NET for Enterprise Portal. MorhpX generally will not direct your code to run on a specific tier, but you as an application developer can control it.

Whether code runs on the server or on the client has performance and security implications, and should be given careful consideration as a part of design. Occasionally it will be correct to methods run on either tier, but usually this is not the case.

As MS move forward implementing tasks in upcoming release, developers will identify which resources to grant access to for a given task. These resources include tables/fields and server entry points. A server entry point is a specially decorated method that runs on the server. Tables/fields accessed inside this server entry point need NOT be identified with the task, greatly reducing the complexity and effort required to implement the task. If the server entry point is NOT executed on the server, then table/field access is still validated, and will fail if the code accesses a table/field that is not included with the task.

So, in short:
Set the RunOn AOT property to Server or Client for new classes, unless you have a reason to leave the default
Include considerations about where the code runs in your design, and look for it when reviewing design documents
Declare static class methods, table static and instance methods with either the "server" or the "client" keyword, unless you have a reason not to
Look for ways to limit direct table and field access in form methods, try to move this into a class

This page MSDN describes where methods run:
http://msdn.microsoft.com/en-us/library/aa891949.aspx. Additional information to cover more object types at http://msdn.microsoft.com/en-us/library/aa634829.aspx.

Iterate all records from grid

2009-07-21T14:53:00.000+06:00

To iterate all record from a grid is accomplished by :

VendOutPaymForParams_FI exportSetupLocal;

for (exportSetupLocal = exportSetup_ds.getNext();exportSetupLocal;exportSetupLocal=exportSetup_ds.getNext())
{
B....
}

Getting rid of the "Loss of precision" warning message

2009-07-14T18:56:00.001+06:00

A question came up at today's webinar where a developer had a (presumably legitimate) reason to cast a real value into an integer value. The X++ language does not allow explicit casting (there's no support for it in the language), but the compiler will do its best to satisfy the user and do the conversion on its own. In this case, however, it issues a warning message, lest this is not what the user wanted.

One solution is to use the anytype type to hold the vaue for conversion and then using the any2int function, as shown below:

static void Job47(Args _args)
{
real r = 3.13;
int i = r; // Warning is issued here
anytype a;

a = r; // Assign to an anytype variable...
i = any2int(a); // ... and back into an int

print r;
print i;
pause;
}
This should be packaged into a function, maybe called int RealToInt(real arg).

Another way would be doing the conversion in managed code (through the System.Convert::ToInt32(object) method), but the performance will not be as good because of the marshalling that needs to take place.

Forthcoming changes to the X++ language

2009-07-14T18:53:00.000+06:00

Very informative link for new X++ release
http://blogs.msdn.com/x/archive/2009/06/29/forthcoming-changes-to-the-x-language.aspx

How to get all changes done in usr layer into project.

2009-07-06T19:56:00.000+06:00

Create a new project and open the project.

Press Ctrl+f3 or click on the icon advance filter/sort on the toolbar of the
project, a dialog with name project filter will be opened.

In project filter, select append and aot.Click select for the query dialog
to open enter the query layer usr in the utillevel range and click Ok to
close query dialog .
Click Ok to close the project filter dialog. This will create a project with the objects of usr layer.

Physics behind the data source refresh(), reread() and research() method

2009-07-03T21:06:00.000+06:00

.refresh() will not reread the record from the database. It basically
just refreshes the screen with whatever is stored in the form cache.

.reread() will only re-read the CURRENT record from the DB so you
should not use it to refresh the form data if you have added/removed
records. It's often used if you change some values in the current
record in some code, and commit them to the database using .update()
on the table, instead of through the form datasource. In this case
.reread() will make those changes appear on the form.

.research() is probably what you want. This will rerun the existing
form query against the datasource, therefore updating the list with
new/removed records as well as updating existing ones. This will
honour any existing filters and sorting on the form.

.executeQuery() is another useful one. It should be used if you have
modified the query in your code and need to refresh the form. It's
like .research() except it takes query changes into account.

In general, you only need to use one of these in any specific
circumstance.

Set the specific row in a grid

2009-07-03T20:41:00.000+06:00

The specific row of grid can be set by calling the dataSource_ds.findRecord(Common _buffer) method. Suppose we want to select third row (i.e Account # 4003) in a customer table grid, here is the code

CustTable_ds.findRecord(CustTable::find('4003'));

Trade & Logistics

2009-06-09T12:58:00.000+06:00

Some T & L notes :

The Purchase order form opens, by default in the Simple view and shows the last purchase order created.
Unit - The purchase unit is the unit of measure that the item is purchased. There is a close relationship between the purchase unit and the inventory unit. For example, the item may be purchased in kilos and stocked in grams.
One-time supplier - For use of a supplier that is not already in the Vendors form.
Invoice account - Invoice account is used if the account number of the vendor you send the invoice to and pay differs from the vendor with whom you place the purchase order.
RMA number - The dialog box displays the Return Merchandise Authorization number (RMA number) when Return Item is selected in the Purchase type field. This number is provided by your supplier and is used for tracking a return item. The field is mandatory when the purchase type is Returned item.
In this field group, specify the language setting for the purchase order. This affects the language that is used for item names and for printing external purchase order documents.
EXAMPLE: Select an item and click Setup - Language - Item
description. Select a language and enter the translation text. Create a new
purchase order and in the Language field group select the language for which
you created a translated text. Print, for example, a receipts list and the
item's name is printed out using the foreign language text.

Trade & Logistics Puchase Order Types

2009-06-09T12:57:00.000+06:00

Types of Purchase Order -

There are 6 Purchase order types:
Journal
Quotation
Subscription
Purchase Order
Returned Item
Blanket Order

Journal
The first Purchase order type is the journal. This type is used as a draft. It does not affect stock quantities and does not generate any item transactions and the quantity on the order line will not be considered in the Master scheduler. It can't be posted
EXAMPLE: A purchase order of the type Journal can be used when importing data by batch; in this manner, the purchase order can be reviewed and evaluated without affecting inventory, on-order, or other numbers.

Quotation
This kind of purchase order is used if the vendor has not yet committed to fulfilling the order if the company has not confirmed the purchase order. Quotation type generates an issue lot with the type Quotation in the inventory and optionally in the Master scheduler.
Unlike the Journal type, the Quotation makes an entry in the inventory transaction table. Making this transaction is what enables Microsoft Dynamics AX to use this information for Master scheduling purposes.

Subscription
This kind of purchase order is used for repeated purchases of the same goods or services. When a packing slip is updated, Microsoft Dynamics AX generates a receipt. When the invoice is updated for the receipt, a new packing slip or invoice entry can be updated for the same purchase line immediately or at some future date. The order will never be at an Invoiced status only Open or Received.

Returned Item
This type is used when you return goods to the vendor. A Return Merchandise Authorization (RMA) number supplied by the vendor is required when entering this kind of order

Blanket Order
This kind of purchase order is used if there is a contract with the vendor and you want to order from the contract. Typically, a company uses blanket orders to receive better pricing conditions as the blanket order quantity is bigger than on single purchase orders. You can create a Release order to release, order, and invoice items until the contract is fulfilled. Blanket orders do not affect stock quantities, do not generate item transactions, and are not included in Master scheduling. Release orders, issued from Blanket orders, do affect all the above.

Trade and Logistics - Sales order Types

2009-06-09T12:54:00.000+06:00

There are 6 types of Sales orders -

Journal
Subscription
Sales Order
Returned item
Blanket order
Item Requirements

Journal
Sales orders of the type Journal resembles purchase orders of type Journal because they are also used as types of draft sales orders.Journals help when bringing data into the system that may not meet quality or other standards, as can be the case with data loads or data keyed by a new or temporary worker.A sales order of the type Journal does not affect stock quantities and does not generate item transactions nor will the quantity on the order line be considered in the Master scheduler.

Subscription
This kind of sales order is used for repeated sales of the same goods or services to the same customer. When a packing slip is updated, Microsoft Dynamics AX generates a packing slip. When the invoice is updated, a new packing slip or invoice entry can be updated for the same sales line. The order never has an Invoiced status, only Open or Delivered.

Sales Order
This kind of sales order is used when the customer confirms that they want the order. When you create a new order, the type can be set to default to Sales order type in the parameters form depending on the client's business process.

Returned Item
This kind of sales order is used when receiving goods back from a customer. A Return Item Number is required for this kind of order and can automatically be assigned by Microsoft Dynamics AX 4.0 by the number sequence set up or manually assigned by the user.

Item Requirements
The Sales order type of Item Requirements is connected to the Microsoft Dynamics AX Project Module. When you create your item requirements in the Project module, you create a sales order of the type Item requirements.

BOM overview and Types

2009-06-09T12:51:00.000+06:00

BOM

BOM is one of the most important documents in a manufacturing company. Like the
recipe for a cake, it is a comprehensive list of all the ingredients required to
make or assemble a finished item. These ingredients are the components, parts
and raw materials that are used.

BOM Types
Item - usually is purchased from outside source
BOM - produced in-house and contains components to go for the finished product
Service - represents a service e.g. hourly rates for services during manufacturing

Ten MorphX Tricks

2009-06-09T12:49:00.000+06:00

Here's a great video from mfp...
http://channel9.msdn.com/posts/mfp/10-MorphX-tricks-in-10-minutes/

WMS in Microsoft Dynamics® AX 2009. Shipping Process Overview

2009-05-27T11:39:00.001+06:00

ntroduction The WMS (Warehouse Managements System) encompasses the core components within average Microsoft Dynamics AX installations that are implemented to manage and run world class warehouses. The WMS functionality is enabled by the configuration Read More...

Changes in Sales and Transfer Order Picking from Microsoft Dynamics AX 4.0 to Dynamics AX 2009

2009-05-27T11:38:00.000+06:00

Overview The purpose of this post is to present the major changes and new functionality that was introduced for sales and transfer order picking in AX 2009. The aim and the idea behind these changes is to move towards a single system for picking that Read More...

Supply Chain Management in Dynamics AX

2009-05-27T11:35:00.000+06:00

Here is a link of SCM in Dynamics AX.

Dynamics Ax 2009 VPC available

2009-05-27T11:33:00.000+06:00

Microsoft have released a Virtual PC image of Dynamics Ax 2009 (the new name for Dynamics Ax version 5)

You can download it and user manuals from here (requires partnersource access)

It's almost 7 GB in total and is designed to work on a single laptop/PC (as opposed to a server)

Dynamics Ax - Task Recorder

2009-05-27T11:30:00.000+06:00

This is a free add-on for Ax that allows you to record whatever you're doing in Ax (forms that open, user input and screenshots) and automatically create documentation for you

So far I've been using it to produce Microsoft Word documents that will become part of a user manual for a bespoke Ax module

This is the first time we've actually managed to get it to work! Whenever we've tried it in the past it just wasn't useable
So for anyone else who's had problems with it, try the latest version, after having used it for several weeks without problems, I can recommend it

It's a LOT easier than taking hundreds of screenshots and cutting/pasting them into a word document

It's by no means perfect though, and there is still a fair amount of editing required before the document that it spews out is presentable enough to be of any use to an end-user, but it does make life easier

You can download it from here (requires partnersource login)

There's a brief but succinct description here at the axaptapedia too

How to traverse multiple selected lines in a grid control by using X++ code in Microsoft Axapta

2009-04-24T12:43:00.000+06:00

This post describes how to use X++ code to traverse multiple selected lines in a grid control in Microsoft Business Solutions - Axapta. Do this when multiple rows of the information in the grid control contain the information which is required to perform the required request.
For example, you can use the following code in the click event of the button if you want to traverse two selected lines when the second row and the fourth row are highlighted in a grid control.

void clicked()
{
CustTable ct;
;
//ct is set to the forms data source and using a cursor goes through each record selected in the grid.
for (ct = DataSource1_ds.getFirst(true) ? DataSource1_ds.getFirst(true): DataSource1_ds.cursor(); ct;ct=DataSource1_ds.getNext())
{
print ct.AccountNum," ",ct.Name;
}
super();
}

Sample X++ code that you can use to disable or to hide a query range in Microsoft Axapta

2009-04-24T12:42:00.000+06:00

The following code sample shows how to use X++ code to create a query that contains three ranges. In the code sample, only one specified range can be changed by the end user. In the code sample, the following conditions are true:
• The first range is not shown.
• The second range is shown but cannot be edited.
• The third range can obtain the input from the end user.

static void QueryStatusTest(Args _args)
{
Query q;
Queryrun qr;
QueryBuildRange qbr,qbr1,qbr2;
QueryBuildDataSource qbds;
VendTable vt;
;

// Create an instance of the query class and then provide a name of "Vendors."
q = new query("Vendors");

// Create a data source that connects to the VendTable table.
qbds = q.addDataSource(tablenum(VendTable));

// Use three different field names to create three ranges.
qbr = qbds.addRange(fieldnum(VendTable,AccountNum));
qbr1 = qbds.addRange(fieldnum(VendTable,Blocked));
qbr2 = qbds.addRange(fieldnum(VendTable,Name));

// Set the values for the three ranges.
qbr.value('3*');
qbr1.value(strfmt('(%1 == %2)',fieldstr(VendTable,Blocked),any2int(CustVendorBlocked::No)));
qbr2.value('Office World');

// Set the status of each range.
qbr.status(1);
qbr1.status(2);
qbr2.status(0);

// Create an instance of the QueryRun class.
qr = new QueryRun(q);

// Verify that the QueryRun form is active, and then parse the tablenum value through the VendTable table.
If (qr.prompt())
{
while (qr.next())
{
vt = qr.get(tablenum(VendTable));
print vt;
}
pause;
}

// Show the SQL statement that is produced by the query.
info (qr.query().dataSourceNo(1).toString());

}
Note: The status method provides the function for each range.

Register User Controls and Custom Controls in Web.config

2008-02-25T11:48:00.000+05:00

In previous versions of ASP.NET developers imported and used both custom server controls and user controls on a page by adding <%@ Register %> directives to the top of pages like so:

Note that the first two register directives above are for user-controls (implemented in .ascx files), while the last is for a custom control compiled into an assembly .dll file. Once registered developers could then declare these controls anywhere on the page using the tagprefix and tagnames configured.
This works fine, but can be a pain to manage when you want to have controls used across lots of pages within your site (especially if you ever move your .ascx files and need to update all of the registration declarations.
ASP.NET 2.0 makes control declarations much cleaner and easier to manage. Instead of duplicating them on all your pages, just declare them once within the new pages->controls section with the web.config file of your application:

You can declare both user controls and compiled custom controls this way. Both are fully supported by Visual Studio when you use this technique -- and both VS 2005 Web Site Projects and VS 2005 Web Application Projects support them (and show the controls in WYSIWYG mode in the designer as well as for field declarations in code-behind files).
One thing to note above is the use of the "~" syntax with the user-controls. For those of you not familiar with this notation, the "~" keyword in ASP.NET means "resolve from the application root path", and provides a good way to avoid adding "..\" syntax all over your code. You will always want/need to use it when declaring user controls within web.config files since pages might be using the controls in different sub-directories - and so you always need to resolve paths from the application root to find the controls consistently.
Once you register the controls within the web.config file, you can then just use the controls on any page, master-page or user control on your site like so (no registration directives required):

Formatting GridView in ASP.NET 2.0

2008-02-15T12:59:00.000+05:00

This is very great site for learning about GridView Control in ASP.NET 2.0.
http://www.obout.com/grid

Issues concerning X++

2007-09-10T12:17:00.000+05:00

This link will show you how to resolve compiler warnings in Axapta.

http://blogs.msdn.com/x/

Dynamics AX Programming of Basic Methods of Tables

2007-09-06T12:32:00.000+05:00

this is very nice link for basic level understanding
http://msdax.blogspot.com/2007/07/programming-of-basic-methods-of-tables.html

Code Coverage of Table Level Methods

2007-09-04T11:33:00.000+05:00

In order to enable code coverage you have to follow some naming conventions or override a specific method on your test class:Naming convention: TableName + Test or simply override the testsElementName() method and returnthe name of your table.(also, override the testsElementType and return UtilElementType::Table;

Specifying empty date values

2007-08-30T12:50:00.000+05:00

If you want to set a date field to an empty date or need to compare if a date field is empty, you can use the datenull() function. It is a method of the Global class and will simply return 01\01\1900.This leads to more things:

You can write dates in Axapta X++ editor using backslashes, e.g. 14\04\2006
An empty date in Axapta is specified as January 1st, 1900.
You can use methods from the Global class without having to write "Global::". So, you can write "if date == datenull()" and you do not have to write "if date == Global::datenull()". This works with all the methods from the Global class.

Documenting business tasks

2007-08-30T12:28:00.000+05:00

A beta-version of the task recorder is available for download from PartnerSource for registered partners of Microsoft Dynamic AX.

The tool is useful in quit many scenarios and we would love feedback from our partners on the usage of it. It can be installed on top of Microsoft Dynamics AX 4.0.