might be interesting

[offenmeier]

Hi, this is not a question, just want to share a little piece of experience.

Recently we had a problem in one of our implementations. Ax (4.0 SP2) would throw a stack trace in standard functionality (that shouldn't had been touched by any of our modifications) like "the function was called with wrong number of parameters". Reindexing/recompilation didn't solve the problem, while there were no compilation errors found. Also we couldn't trace into method where the stack trace was thrown, because debugger just wouldn't step in to the method.

The problem was rather silly though. In our modifications one of developers overridden a method in SalesFormLetter class and added a default parameter to the method:

method1(str _parm1, str _parm2, boolean _always = true)

..which is allowed and totally legal. But what he didn't do is that he didn't check if any of SalesFormLetter children already overridden this method. SalesFormLetter_PackingSlip had a method:

method1(str _parm1, str _parm2)

..which after our modifications turned to be totally illegal, because now children class had an overridden method with less parameters then parent class. This situation didn't produce compilation errors, but when calling SalesFormLetter_PackingSlip.method1() Ax would throw the stack trace.

The solution was to add a default parameter to SalesFormLetter_PackingSlip.method1() - and never use it:

method1(str _parm1, str _parm2, [I]boolean _always = true[/I])

[Logger]

Для Ax 3.0 SP3 в подобных случаях вообще клиент падал.