Error executing code, wrong variable assignment

I composed a post regarding “Error executing code” error executing code long time back at blog spot, I thought to shift this post here now. This post is still the useful. Please find the link at the address below

http://dynamicsaxposed.blogspot.com/2009/08/error-executing-code-wrong-variable.html

Comparison between SAP and Dynamics Ax

Hi all-

I found some good links regarding SAP vs Dynamics AX. This will give you idea where we stands, what our product Dynamics Ax is all about? And can we even compare SAP with dynamics AX?

Those of you who have already read these articles, please ignore this email J.

SAP vs dynamics AX

http://download.microsoft.com/download/c/f/3/cf33cf2c-21a2-4a62-b309-8f193738dd4e/ax4.0_competitive_guide_vtr_en.pdf

Why Dynamics Ax is better than SAP

http://dynamics-ax.blogspot.com/2007/01/why-dynamics-ax-beats-sap.html

Why you should migrate from SAP to Dynamics Ax

http://www.touchstone.co.uk/products/enterprise_resource_planning/microsoft_dynamics_ax/ms_dynamics_ax_vs_sap.aspx

This is what SAP expert says about dynamics AX

http://searchmanufacturingerp.techtarget.com/generic/0,295582,sid193_gci1326035_mem1,00.html

Ways of implementing “Go to main table” functionality in Ax

I was working on the “GO to main table” Functionality today and came across many different techniques that AX use for implementing this functionality. So I thought to note it down all the techniques here. There are 3 ways of implementing this functionality

1. Define the relationship with the table on the EDT.

2. Define the Form in the “FormRef” property of the table in the data dictionary

3. Override the jumpRef(…) method at the control level or the dataSourcefield level

Args args; MenuFunction menuFunction; if (!this.RecId) { return; } args = new Args(); args.caller(_caller); args.record(this); args.parmEnum(AllChosen::Chosen); menuFunction = new MenuFunction(menuitemdisplaystr(LedgerTransVoucher1), MenuItemType::Display); menuFunction.run(args);

Now that we have so many options, the question is why we have so many methods and what the scenarios in which these methods are used.

1. EDT “go to main table” functionality

This functionality is normally used when you don’t have a normal foreign key à primary key relationship between the tables and you are dropping a field into another table. This practice is going to be removed eventually from AX. The reason for this having relationship on the EDT is not a good practice and have high impact when it comes to reusability.

For instance, ProjId EDT.

2. Table formRef “Go to main table” functionality

This is used when you have a foreign key relationship between the tables on the basis of RecId.

3. “Go to main table” functionality by jumpRef

This is used when you do not have the direct relationship or field (which has the relationship on the EDT) between the two tables and still you want to explicitly provide this functionality.

Regards,

Fawad

How to get DateNull in axapta x ++

One of my co new bie developer with the Dot net background had really hard time in figuring out the dateNull in x++ due to two reasons

1. X++ does not have intellisense like Dot net which could help the newbie like my colleague
2. The null value in  x++ debugger is shown as “Zero (0)”. So lots of new bie take the null value for date time as 0 and go in wrong direction

So i just thought to do a simple post on it. I know for a senior or the developer at mid level may find this simple and irrelevant to be posted at the blog, however i think this may help the new developer who are at the edge of starting new career in x++.
So here it goes

DateNull for the date can be checked by two ways

1. Global::DateNull()
2. or like this
   if (endDate != mkdate(1,1,1900)

The minimum value for the date in x++ is 1/1/1900 and max value is 12/31/2154

If you have utcDateTime here is how you can set dateNull and maximum value

todayDate = DateTimeUtil::minValue();
maximumDate =  DateTimeUtil::maxValue();
blankUtcDate = utcDateTimeNull();

Hope this help