Code Profiler

The Code Profiler measures the execution time of individual lines of code. Use this tool to find performance bottlenecks and to help understand code that was developed by others.

     How to use Code Profiler

Ø  Click Tools > Code profiler to open the Code Profiler tool.

Ø  Navigate to the functionality that you want to test. For example, navigate to the appropriate place in the Navigation Pane.

Ø  To limit the results displayed, check the Trace depth enabled check box, and then type the number of levels that you want to be displayed in the results.

Ø  Click Start. Use the functionality you want to test. When testing is complete, click Stop. The system now saves all logged data to the database. This might take quite some time because a database record is created for each executed line of code.

Ø  Write a description of your code profile in the Summary dialog.

Do not select the Calculate line total check box. If you need to calculate line totals later, use the Profile runs form.

Ø  Click OK.

The Profiler runs form opens. This enables you to view data collected by the profiler.

   To view the data that is collected by the code profiler

Ø  Click Profiler runs.

Ø  Select the data set that you want to view.

Ø  Click the Statistics tab to view a summary of the information for the code profile.

Ø  Click one of the following four buttons to view more detailed data:

Call tree – Shows you a hierarchy of method calls

Profile lines – Shows a list of all lines of code that are executed, making it easy to find which lines of code took the longest to execute.

Traverse – Shows a sorted list of the time that was spent in all methods, combined with the sum of the time spent in sub calls, plus the sum of the time spent in the method, depending on the origin of the call.

Totals – Allows you to select summaries of the time spent in lines, methods, and objects.

    The Call tree, Profile lines, and Traverse forms show raw data. Aggregated data is available in                            the Totals options.

  Using code Profiler in X++

As an alternative to the graphical user interface, you can control the code profiler directly from your X++ code. For this purpose there are two macros:

·         #Profilebegin()

·         #ProfileEnd

These two macros have to be in the same level in a method.

static void codeProfilerTest()

{

    int   i, j;

    ;  

    #profileBegin("test")  

    

    for(i=1;   i<=10; i++)

    {  

        j+=   i*i;

    }  

    

    info(strfmt("%1",j));  

    #profileEnd  

}

You will then have to find the collected data under Tools > Code profiler > Profiler runs, and process the data yourself by selecting Totals > Calculate sum.

Ax & TFS Daily Development Version Control

To check new objects into TFS:

1. If the object exists and you have not modified the object, modify it first.  If the object is a completely custom object, create it first.

By default objects do not exist in version control.  For example, objects that exist only in the sys and syp layers would not be checked into TFS because they can be recreated simply by reinstalling AX.  Version control is for tracking changes to customizations made to existing objects or for completely custom objects.

2. In the AOT right-click on the object and choose Add to Version Control
3. Once you have a collection of objects ready for check-in, in the AOT go to Version control > Pending Objects and check-in the objects in the list

-When objects are added to version control, xpos are created for the objects and saved into the local repository on the developer’s machine.

-When the objects are checked into version control, the xpos in the local repository are copied up to the central shared TFS repository.

4. In the form where you check in the objects there is a Work Items tab.

-Enter in the ID of the TFS task to tie this check-in to and in TFS’s Sharepoint site in this history for the task you’ll see your check-in against the task and you will see the individual objects that were checked-in.

To check out objects previously added to version control:

1. In the AOT right-click on the object and choose Check Out
2. Make your changes to the object
3. Click on Version control > Pending Objects and check-in the objects in the list

-Once one developer has an object checked out, another developer will not be allowed to check out that same object

To view the history of an object:

1. Right-click on the object and choose History
2. In the form that opens you can select a version from the list and click the Get button to import that version of the object into your AOT.
3. In the form that opens you can click the View file button to open the xpo for a particular version of the file

To synchronize to changes checked into the central repository by yourself or other developers:

1. Click on Version control > Synchronize
2. In the dialog that opens mark the Force checkbox and click OK.

-This will force version control to overwrite any changes you’ve made to objects in your local AOT that aren’t checked out or under version

control.

3. In the form that opens, mark the model you want to synchronize to.

-When you synchronize to the central repository all of the xpos that have been checked in since the last time a sync was executed on the machine, are copied from the central repository to the local repository.

-Once the xpos exist in the local repository they are imported into AX and a database synch and compile are performed for those imported objects.

To check out the label file and add new labels to it:

1. Click on Tools > Labels > Label editor
2. The label editor form will open and at the top click on the Get Latest button to ensure you have the latest copy of the label file.
3. At the top of the label editor form click the check-out button to check out the label file.
4. To create a new label, in the label editor form, click the New button and save the label.
5. The label will be given a temporary label id like $@ABC123.  Use the temporary label id in your code that uses the label.
6. Once the labels have been created, click Version control > Pending objects and check-in the objects in the list.  (The label file will be one of the objects.)
7. When you check in the label file, a permanent label id will be assigned to each new label.

-If the code you have that uses those labels is still checked out or is being checked in with the label file, the temporary labels will be automatically replaced with the permanent label id.

-If the code you have that uses those labels is not checked out, after the label file is checked in and the permanent label ids are known, you’ll have to go through your code, check out the objects, and manually change the code to use the permanent label id.

Validates an email address

Validates an email Address

SysEmailDistributor Class

client server public static boolean validateEmail(str _email)

Run On  Called



Parameters  _email

Type: str Email address 



Return Value  Type: boolean


true if email address is valid. false otherwise. 



Example for Email Validation 

public static void sysemail(args _args)
{
   boolean isvalid;
  // Here change the email address and check
   isvalid=SysEmailDistributor::validateEmail("xyz@gmail.com");
 
  info(strFmt("%1",isValid));
}