Tip: How to find out where that error message comes from

Have you ever got an error or info message in Axapta saying "Cannot post...." and wanted to know where that error is coming from?
Here's a tip how to find out where the info message is thrown.

First, add a breakpoint in the Info class, method add:


After that, run the script that throws the error. As soon as the error message is thrown, the Axapta debugger will pop up:

At the lower part of the screenshot, you can see the call stack (if not, go to menu "View" and activate menu item "Call stack").
In the call stack, you can double-click on any line and the debugger will go back to it. Let's say we clock on the third line of the screenshot above. The debugger will take us to the Class TaxCov, method TaxLedgerCov:

You can see that the debugger put us exactly to the place where the error was thrown.

With the above method, it's pretty easy to find your way around the infos that Axapta gives you.

ATTENTION: Be careful when upgrading to Axapta 3.0 SP4

When you upgrade your Axapta 3.0 SP1-3 to the latest Service Pack 4, make sure you import the Hotfix HF30SP4_011 first.
If you do not install it, the upgrade may run for an extremely long time (but: no data will be harmed).
You can get the hotfix from Partnerguide or your Axapta partner.

Axapta performance comparison Win 2003/2000

If you want to know whether it's better to run Axapta on Windows 2003 or Windows 2000, here is what Microsoft found out:

http://download.microsoft.com/...

How to set-up COM+ for Axapta correctly

Ever wondered why your COM connection was working while you were logged on to the PC and not working without being logged on?
Here's a short guideline how to set-up your COM+ correctly:

1. You have to be logged on to the PC as a Local Administrator. Create a service account under which the COM+ should be running, this account must be local administrator on the PC. Log on with that account.
   
2. In Axapta Config Utility: an Axapta User must be entered (on General Tab). This user must of course have the necessary rights in Axapta.
   
3. In Axapta Config Utility: if the User has a Password, the Password must be entered (on COM Tab).
   
4. Now (and only now) the COM+ component may be registered --> Config Utility, Tab “Business Connector”, Button “Register”. Of course you have to use the "Register COM+" option and the right dll file.
   
5. In the Control Panel/Administration/Component Services: go to the Axapta COM+ Component (should be located under “Component Services / Computer / Workstation / COM+ applications / Navision Axapta Business Connector”.Open up the properties for the Axapta COM Connector. Go to the Identity Tab.Here, by default, the option “Interactive User” is chosen.Change this to: This User. Enter the user id (+domain) and password of the user you have logged in the PC (which should be the same as in 1., so this must be the local administrator).
   

If these guidelines are followed, the COM+ Axapta Connector will run even if nobody is actually logged on the PC. But be cautious: the COM+ connector will use the default Axapta configuration for the domain user that you entered in the component service. If you do not follow the 6 rules above, your COM+ might still not work.

Testing AOS Latency

Wanted to know how big your AOS latency really is?
On many Axapta pages you can read that you should not test it with the "ping" command but with Axapta's built-in feature to test the latency. And so it works:

Start the system monitoring window by double-clicking the symbol as in the screenshot below(it's where area where the green arrow is displayed while Axapta is doing something).



In the System monitoring window, you can test the Latency by clicking on the “Test” button. Do that a couple of times and measure the times.
In the system monitoring window, also a Pseudo-simulation of a certain bandwidth and/or latency can be tested.

Enter a bandwidth and latency time, click on “Set as current” and your system will simulate that it runs over a connection with those settings.

There is also a startup-parameter for simulating the remote connection.

-bwsim=8000:50:1

to have a bandwidth of 8000 KBps (i.e. 64 kilo bit per sec)50 msecs latency 1 indicates that only data is penalized (not application objects)2 indicate include application object

Data dictionary changes in 3-tier applications

If you have a 3-tier AOS application that is running on several AOS in a cluster, sometimes developing can be a pain.

Besides the old known trick of duplicating the menu items SysFlushAOD, SysFlushData and SysFlushDictionary and set the duplicates to run on server, here's another hint.

The AOS will know about each other's changes in the AOT in some minutes time. But this will not work if you make changes in the data dictionary.

Following example: in a table, you create a new index with several fields and synchronize it to the database.
After that, you enter Axapta on another AOS. What will you see in the index list for the table ?
--> The index you just created is called "UNKNOWN" (but has the fields inside).

What you have to do now is call the SysFlushDictionary menu item (the one that is running on server or even better both of them, but first the one running on server).
Et voilá. You will see the index in the AOT.

Welcome

Welcome to the Axapta Blog Site.

This blog will deal with things around Axapta as well as provide some sample programming projects.