Fred Shen

• Start -> All programs -> Administrative Tools -> Component Services.
• Expand Component Services
• Expand Computers
• Expand My Computer
• Select the DCOM Config item
• Select the Microsoft Word Document item.
• Right click and select Properties
• Under Launch and Activation Permissions select the Customize option.
• Click the Edit button
• Click the Add button to add a new account to the list.
• Click the OK button
• On the dialog that is displayed enter Network Service as the account name.
• Grant Network Service the launch and activate permission.

This will tell you how to use Common Language Runtime Interoperability feature in Dynamics AX 4 to reference a web service.  There is a pretty good discussion about this on Microsoft MBS community by Dilip and Mike Frank.

To continue, at least you need to have Dot Net Framework SDK 2.0.  (Not Visual Studio .Net) We will use the language translation service on www.stanski.com as the referenced web service.

Procedure:
Download and Install .NET Framework Version 2.0 Software Development Kit.

Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.

At the command prompt, run the following command:
Wsdl /l:cs /protocol:soap http://www.stanski.com/services/translate/translate.asmx
This will generate a C# source code file of proxy classe, which in this situation is TranslationService.cs

Then we need to edit TranslationService.cs file to add namespace for it.
Use NotePad to edit TranslationService.cs, the edited codes should look like
//------------------------------------------------------------------------------
// <auto-generated>
…
namespace DemoAXWebService //Add namespace declaration
{
    using System;
    …
    …
}//End namespace declaration

Compile the cs file to dll file. Type this in the command prompt
csc /t:library TranslationService.cs

This will generate the TranslationService.dll.
Copy the TranslationService.dll to \Program Files\Microsoft Dynamics AX\40\client\Bin.

Start Microsoft Dynamics AX 4.0
Open Application Object Tree, and locate the Reference node. Right click, select Add Reference and register the TranslationService.dll in Dynamics AX.

Create a new job named TestWebService
static void TestWebService(Args _args)
{
    DemoAXWebService.TranslationService translateService
     = new DemoAXWebService.TranslationService();
    str strLanguage, strMessage;
    str translateResult;
    ;

    strLanguage = 'en_de';
    strMessage  = 'Test Web Service';
    translateResult = translateService.Translate(strLanguage, strMessage);
    Info(translateResult);
}

Run the job, you will get the result “Test-Netz-Service”.

Query range value expressions can be used in any query, where you need to express a range that is more complex than that made possible with the usual dot-dot notation.
Especially to use Or clause in query, you definitely need to use Query Range Value Expression.

Today I just want to investigate more about the date data type in Query Range Value Expression.
To retrieve records where the transaction date is before 21st June, 2006. You can use Date2StrXpp() to format the date:
    queryBuildRange.value(strFmt('(TransDate <  %1)', Date2StrXpp(21062006)));

    dateInt  = (dayInt-1)*Power(2,16) + (monthInt-1)*Power(2,8) + (yearInt-1900);
   

    queryBuildRange.value(strFmt('(TransDate <  %1)',  dateInt));

Some Axapta system administrator may feel it is really annoying that Axapta allows the user to create multiple Axapta sessions and log in as the same user. If you want to give the user notification prior to logging in as the same User ID, here comes the solution.
Under the Info class, modified the startupPost method like the codes below:
void startupPost()
{
    int         counter;
    int         num = 0;
    int         maxSessions = Info::licensedUsersTotal();
    xSession    session;
    UserInfo    userInfo;
    UserId      currentUserId;
    ;

    currentUserId = curuserid();
    for(counter = 1; counter < maxSessions;counter++ )
    {
        session = new xSession(counter, true);
        if(session && session.userId())
        {
            select firstOnly userInfo
                where userInfo.id == session.userId();

            if (userInfo && (currentUserId == session.userId()))
            {  
                num++ ;
            }
        }
    }

    if (num > 1)
    {
        if(box::yesno("The same user id can't log in twice. Do you want to log in anyway? ",
                   DialogButton::Yes, "Log in", "Log out") == DialogButton::No)
        {
            infolog.shutDown(true);
        }
    }
}

Please notice that, if you modify the startupPost method of Application class, that works only in 2-tier environment. For both 2-tier and 3-tier environment, it is recommended to modify the startupPost method of Info class.

static void TestDateTimeConversion(Args _args)
{
    LoginProperty             loginProperty = new LoginProperty();
    ODBCConnection      con;
    Statement                    stmt;
    str                                  sqlString, result;
    ResultSet                     resultSet;
    ;

 

    loginProperty.setServer('LocalServer');
    loginProperty.setDatabase('AXDB');
    loginProperty.setUsername('bmssa');
    loginProperty.setPassword('bmssa_pwd');
    con = new ODBCConnection(loginProperty);

    sqlString =   "SELECT * FROM LedgerTrans WHERE DATAAREAID=' "

                         + curExt()

                         + "' "
                         + " AND TRANSDATE<CAST(' "

                         + date2str(str2date('22/02/2006',123),321,2,3,2,3,4)
                         + " ' AS datetime) "
                         + " AND TRANSDATE> CAST(' "

                         + date2str(str2date('20/02/2006',123),321,2,3,2,3,4)
                         + " ' AS datetime) ";

    stmt = Con.createStatement();
    resultSet = Stmt.executeQuery(sqlString);
    resultSet.next();
    result = resultSet.getString(1);
    if (result)
    {
        info(result);

    }
    else
    {
        info( "No record! " );
    }

}

1. 
   Keep the "width" of your indexes as narrow as possible. This reduces the size of the index and reduces the number of disk I/O reads required to read the index, boosting performance.
2. 
   If possible, try to create indexes on columns of Integer data type instead of string.  Integer values have less overhead than string values.
3. 
   Don't use Real data types for primary keys, as they add unnecessary overhead and can hurt performance.
4. 
   Indexes on narrow columns are preferable to indexes on wide columns. The narrower the index, the more entries SQL Server can fit on a data page, which in turn reduces the amount of I/O required when accessing the data.
5. 
   Reduce the size of the index, thus decreasing read I/O during the join process, and increasing overall performance.