One of the cool things about unit of work (UoW) is the capability to use a custom user connection. If you would like a set of DML operations to be executed on a separate user connection then that is possible with UoW. If you have legacy code that uses RecordInsertList and want to use a custom user connection then you should rewrite the code using UoW.

Here is an example of how to use UoW with a custom user connection:

static void UoWTest(Args _args)
{          
    Table1 table1;
   
    // Define a new user connection
    UserConnection uc= new UserConnection();
   
    // Define a new UoW
    unitOfWork uofw = new UnitofWork();        
           
    // Add a table buffer to insert on save changes in the UoW
    table1.Field1 = 'foo';
    uofw.insertonSaveChanges(table1);           
   
    // Perform additional interactions that you 
    // want to club together with the UoW
    // by calling insertonSaveChanges, updateonSaveChanges
    // and deleteonSaveChanges 
   
    ...

    // Finally pass the user connection to
    //the UoW to use on SaveChanges
    uofw.saveChanges(uc);
}

In Dynamics AX 2012, information about the user sessions can be directly included in the SQL connection context. Adding  this information has a small performance overhead. Therefore, it is not turned on by default. To include user session information in the connection context perform the following steps:

1. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dynamics Server\6.0\01\Original (installed configuration). The last key, Original (installed configuration), is the key name for the current server configuration. If your system uses a different configuration that the original installed configuration, navigate to the currently active configuration.
2. Create a string registry value called ‘connectioncontext’ and set the value to 1.
3. Restart the AOS.

Next open SQL Server Management Studio and run the following query to look at all the sessions related to Microsoft Dynamics AX:

select cast(context_info as varchar(128)) as ci,* from sys.dm_exec_sessions where program_name like '%Dynamics%'

Here’s the sample output. Let’s take a closer look at the ci column.

The first two items in the connection information are AX user id and the AX session id. So for SQL session_id 60 the user is ‘Admin’ and AX session id is 3. Next we can open the “Online Users” form to find the user session associated with the SPID.