Axapta 3.0 Kernel Rollup 2 released !!!

The Kernel Rollup 2 has been released. Here are links to the fix list and the readme:
KR2_Fixlist.htm

(Edit: I removed the link to the readme due to copyright reasons)

Search for item id in config id lookup (in queries)

We had the following problem: we are using a lot of config ids for items. Now, when you click on the lookup button of a config id field in a form, Microsoft has made some changes so it will only show you the configs of the current item (in the form).
This does not work, however, in a standard query (like a report query). There, the lookup for config id will show you *all* config ids of *all* items in Axapta.

The easiest possible way to make it a little more usable for me was to add the ability to search for item ids in this lookup (which is not possible in standard).

So please download the changed form here and enjoy: http://www.geocities.com/axaptafreak/Files/configidlookup.zip

Display session's AOS name in online user form

When you have more than 2 AOS servers in your Axapta setup, you might experience the following problem: the online user form will only tell you whether the user displayed is currently working on the same AOS as you (then it will say "thin") or on another AOS (then it will say "NotAOS").

As long as you only have 2 AOS that's not a big problem, as "Thin" will mean the user is on the same AOS as you and "NotAOS" means he is on the other one.

But if you have 3 or 4 AOS, "NotAOS" will not tell you on which of the other AOS the user is working on.

So, here you can download a little project where one column is added to the online user form displaying the AOS setting of the user (including AOS cluster information):
http://www.geocities.com/axaptafreak/Files/hw_sysusersonline_aosname.zip

You will see the additions I made when you compare the elements in Axapta. It's not a big deal but I needed that info very often so here it is for you.

Axapta Audit Trail (Table TransactionLog)

2 things about the audit trail:

1. Palle Agermark has posted an interesting article about the audit trail and when records will be created depending on the TTS level of the application. You can read it here: http://blogs.msdn.com/palle_agermark/
   
   

2. We recently ran into the problem that we got error messages in Axapta saying "Cannot create a record in Audit Trail. The record already exists." We are running Axapta 3.0 SP3 (upgraded some years ago from 2.5). Unfortunately, the error is repaired in SP4, but you can actually repair it also in SP3.
   
   Go to the class "ReleaseUpdateDB_V30toV30SP" and copy the method "RepairTransactioIdPerTableV30toV30SP" into a new job. (NB: The method will only exist in a SP4 or SP5, of course).
   In the job, you have to comment the first line after the variable declaration, that is this.tableProgress(tablename2id('dataArea'));
   You can run the job and all your entries in the SystemSequences table will be corrected.
   
   Please also check the table SQLSYSTEMVARIABLES in your database. Check the value for the parm "Index". If it is below 256, you also have a second problem -> please write a comment and will explain further what to do.