Dynamics Ax Forum: September 2011

Setting up Outlook Sync from Dynamics AX

In the demo VMs you have Outlook installed and connected to a basic email server. This is used in many places like alerts, workflow, etc. You can also use the sync features that exist in the AX CRM. For example syncing Contacts, Appointments, Tasks etc.

This video walk through the process of setting up an employee to sync to Outlook:

Double click to watch full screen

Setting up Outlook Sync from Dynamics AX - Reflections on Microsoft Dynamics AX - Site Home - MSDN Blogs

Peter Villadsen and Gustavo Plancarte: X++ to MSIL | Charles | Channel 9

Peter Villadsen and Gustavo Plancarte: X++ to MSIL | Charles | Channel 9:

30 minutes, 47 seconds

Download

Right click “Save as…”

High Quality WMV(PC, XBox, MCE)
MP3(Audio only)
MP4(iPod, Zune HD)
WMA(Audio only)
Mid Quality WMV(Lo-band, Mobile)
WMV(WMV Video)

Dynamics Program Manager Peter Villadsen and Software Developer Gustavo Plancarte teach us about a new tool they've developed that translates X++ byte code into MSIL. We learn a lot of history along the way and gain insights into the process of taking X++ into the .NET age.

Microsoft Dynamics features a proprietary language called X++ (basically a superset of Java, with some strong data primitives added) and a complete stack (compiler, interpreter and debugger) that goes with it. The new feature Peter and team have developed is a tool to generate managed code from the X++ intermediate language produced by the X++ compiler. This will have profound impact on the performance of the business applications written in X++, and it very clearly points to where they'll be going in the next few releases of Dynamics Ax.

Application Object Patch Layers [AX 2009]

Application Object Patch Layers [AX 2009]:

In addition to the 10 application object layers in Microsoft Dynamics AX, there are also patch layers. The patch layers are called SYP, GLP, BUP, VAP, CUP, and USP. This topic describes the patch layers and why you should use them.

The patch layers are designed to make it easy to incorporate updates in your application. The basic idea is that when a minor update or correction is made, it is distributed in a patch file, for example, Axsyp.aod. When a patch file is present, the modified objects in the patch file take precedence over the regular application objects and are automatically used. The following illustration shows the application object layers and the patch layers.

AX Layers plus Patch Layers

The patch files use the same application object number series that the regular files use.

Using patch layers allows you to easily create and distribute an update, for example, by using the Internet, without interfering with the existing application. When you subsequently incorporate the update in the regular layer file, you can delete the patch file that is named Ax??p.aod and the index file Axapd.aoi.

Application Object Layers [AX 2012]

Application Object Layers [AX 2012]:

Application object layers hold everything that is displayed in the Application Object Tree (AOT). This topic describes application object layers and how they are used in Microsoft Dynamics AX.

Layers are a hierarchy of levels in the application source code that enable you to make modifications and additions without interfering with the application objects in the next lower level. When you make an object modification on one level, the modification overshadows the object on a lower level. You could, for example, decide to add e-mail information to a standard form. The addition would be saved on your level only. The revised form replaces the standard form. However, you can always return to the original form at the next lower level by removing the new form.

Three customer groups have an interest in adding and modifying application objects:

Application developers who create the standard application.
Business partners.
End users of Microsoft Dynamics AX.

The following table describes the application object layers in Microsoft Dynamics AX.

Layer	Description
SYS	The standard application is implemented at the lowest level, the SYS layer. The application objects in the standard application can never be deleted.
GLS	When the application is modified to match country/region specific legal demands, these modifications are saved in a separate layer, the GLS layer. If an application object, for example, a form, is modified in the GLS layer, the modifications are saved in the GLS layer only and the modified version of the form is used.
HFX	HFX is an application object patch layer reserved by Microsoft for future patching or other updates. For more information, see Application Object Patch Layers.
SL1, SL2, or SL3	A layer where the distributor can implement vertical partner solutions. SL is an abbreviation for SoLution.
BUS	When a business partner creates their own generic solution, their modifications are saved in the BUS layer and the top level application objects are used.
VAR	Value Added Resellers (VAR) can make modifications or new developments to the VAR layer as specified by the customers or as a strategy of creating an industry specific solution. Such modifications are saved in the VAR layer.
CUS	The supervisor or administrator of an end-user installation might want to make modifications that are generic to the company. Such modifications are saved in the CUS (CUStomer) layer.
USR	End users might want to make their own modifications, such as in their reports. These modifications are saved in the USR layer.

Each layer is saved in a separate file that is named Ax<layer>.aod, for example, Axsys.aod for the SYS layer, Axsl1.aod for the SL1 layer, and so on. The .aod extension is an acronym for Application Object Data.

In addition to the 10 layers, most layers also have a patch layer. For more information, see Application Object Patch Layers.

Microsoft Dynamics AX 2012 for Developers

Microsoft Dynamics AX 2012 for Developers:

AX2009 SecurityProfiler Tool - Microsoft Dynamics AX Technical Support Blog - Site Home - MSDN Blogs

AX2009 SecurityProfiler Tool - Microsoft Dynamics AX Technical Support Blog - Site Home - MSDN Blogs:

UPDATE: This tool has been updated to support list pages (e.g. Sales Table List Page, Customers List Page) that use queries as their datasource (22/June/2010)
UPDATE: This tool has been updated to use the language from Infolog, and the sort order on the report has been changed to descent on the ProfileId (29/Oct/2010)
--------------------------------------------------

The attached tool, an xpo file inside the zip file, tracks what security keys are being used when a user navigates thru the application.
The existing AX class we hook into gets used every time a form or report is opened in AX so the tool will slow performance down – so don’t load this in a production environment.

Also this doesn’t work for menu items that call classes but we don’t expect that to be a big deal.
The tool is useful for sorting out security in a test environment.

In order to use this tool go in as an Administrator that has access to all of the forms and reports in the system:

1. Extract the xpo file from the attached zip file and Import it into AX

2. Close the AX client and re-launch it again. This step is important because we have added 2 menu items to the Administration menu and they won’t show up until AX is reloaded.

3. Under Administration go to Security Profiler.

4. Click the Start Profiling button – and leave this form open.

5. Navigate to the forms and reports you want to gather security key information about.

6. Click the Stop Profiling button in the Security Profiler window (the same window opened in step #4).
a. A form will open showing you all of the security keys that were hit while you navigated thru the system.
b. To print out the results listed in the report click the Print report button and click the Default button on the print options dialog that opens.
c. To view your existing security profiles click Administration > Security Profile Results

This tool should not be loaded into a production environment.

Disclaimer: This programming example is for illustration purposes only. Microsoft disclaims all warranties and conditions with regard to use of the programming example for other purposes. Microsoft shall not, at any time, be liable for any special, direct, indirect or consequential damages, whether in an action of contract, negligence or other action arising out of or in connection with the use or performance of the programming example. Nothing herein should be construed as constituting any kind of warranty.

--------------------------------------------------

--author:	Becky Newell
--editor:	Daniel Durrer
--last edited:	Daniel Durrer (29/Oct/10)

PrivateProject_SecurityProfilerProject2009_29Oct10.zip

Microsoft Dynamics AX 2009 Facility Management Sample - Home

Microsoft Dynamics AX 2009 Facility Management Sample - Home:

Resource Page Description
The Facility Management sample application for Microsoft Dynamics AX 2009 provides an example of how to implement common functionality in Microsoft Dynamics AX. Use it to learn about how to implement your own module or integrating application.

Audience
The Facility Management sample is intended for developers who want to see an example of the types of integrations they can create for Microsoft Dynamics AX 2009. Basic knowledge of Microsoft Dynamics AX 2009 is assumed.

Issue Tracking
Readers are invited to submit issues and suggestions using the Issue Tracker. When reporting an issue, please provide as much information as possible that describes the problem.

Other Resources
To learn more about developing integrations for Microsoft Dynamics AX 2009, please refer to the Microsoft Dynamics AX Developer Center:http://msdn.microsoft.com/dynamics/ax

How to: Print a Range of Pages from a Report (MorphX Reporting Tools)

Print a specified range of pages from a report by using the PrintJobSettings.allPages, PrintJobSettings.from, and PrintJobSettings.to methods.

Example

In the following example, pages 2–4 from a report are printed to a .pdf file. The ReportRun.setTarget method specifies a file as the print medium. The printJobSettings.format and printJobSettings.fileName methods specify the file format and the file name.

other

Copy

static void printToPDF(Args _args)
{
    Args                args;
    ReportRun           rr;
    str reportName = 'Cust';
    ;

    args = new Args(reportName);

    rr = new ReportRun(args,'');
    
    rr.setTarget(Printmedium::File);
    rr.printJobSettings().format(PrintFormat::PDF);

    rr.printJobSettings().fileName("C:\\Cust_ReportRange.pdf");
    
    rr.printJobSettings().allPages(false);
    rr.printJobSettings().from(2);
    rr.printJobSettings().to(4);

    // Disables forms that enable users to modify
    // the report query and print settings.
    rr.query().interactive(false);
    rr.report().interactive(false);

    rr.run();

}

Walkthrough: Creating a Precision Design Report [AX 2012]

In this walkthrough, you will create a vendor invoice report. You will use SQL Report Designer to create a precision design for the report. The following illustration shows the report that you will create in this walkthrough. Report precision design

Note Note

The data that displays in your report may vary depending upon the sample data that is available to you.

This walkthrough illustrates the following tasks:

Defining queries
Creating a reporting project
Creating a precision design report using SQL Report Designer

Prerequisites

To complete this walkthrough, you will need:

Microsoft Dynamics AX with sample data
Note
In this walkthrough, you will use the VendInvoiceJour and VendInvoiceTrans tables. Therefore, these tables must be populated with data.
Microsoft SQL Server 2005
Microsoft Visual Studio 2008 with Service Pack 1
Microsoft Dynamics AX Reporting Tools for Microsoft Visual Studio

Defining Queries

There are several ways to retrieve data for reports. In this walkthrough, you will create queries within the Microsoft Dynamics AX development environment. The following procedure explains how to define the queries that will be used to retrieve data for a vendor invoice report.

To define the queries

Open Microsoft Dynamics AX.
In the AOT, right-click the Queries node, and then click New Query.
Right-click the node for the query, click Rename, and then type InvoiceJournal.
Expand the node for the InvoiceJournal query.
Right-click the Data Dictionary node, and then click Open New Window.
In the new window, expand the Tables node.
Locate the VendInvoiceJour table and drag it onto the Data Sources node for the query.
Expand the node for the VendInvoiceJour data source.
Right-click the Ranges node, and then click New Range.
Right-click the VendGroup node and then click Properties. Select the node for the range, and in the Properties window, set the Field property to InvoiceId.
In the AOT, right-click the Queries node, and then click New Query.
Right-click the node for the query, click Rename, and then type InvoiceTransaction.
Expand the node for the InvoiceTransaction query.
Locate the VendInvoiceTrans table and drag it onto the Data Sources node for the query.
Expand the node for the VendInvoiceTrans data source.
Right-click the Ranges node, and then click New Range.
Select the node for the range, and in the Properties window, set the Field property to InvoiceId.
Save the queries.

Creating a Reporting Project

Next, you will create a reporting project in Microsoft Visual Studio. When you create a reporting project, you can choose from two project templates: Visual Basic and Visual C#. In this walkthrough, you will use the Visual C# template.

To create a reporting project

Open Microsoft Visual Studio.
On the File menu, click New, and then click Project. The New Project dialog box displays.
In the Project Types pane, click the Visual C# node. In the Templates pane, click Dynamics AX Reporting Project.
In the Name box, type SampleVendorInvoiceReport, and in the Location box, type a location.
Click OK.
A reporting project contains a model by default. A model is a file with the .moxl file name extension. When a reporting project first opens in Microsoft Visual Studio, the model automatically displays in Model Editor. It contains a default report named Report1.

Creating a Precision Design Report Using SQL Report Designer

Now that you have created a reporting project, you are ready to create a precision design report to display the data returned by the queries that you created in Microsoft Dynamics AX. To do this, you will first define datasets for the report. Then, you will configure the parameters that are created for the datasets. Finally, you will use SQL Report Designer to define the report layout.

To define datasets for the report

In Model Editor, right-click the Report1 node, and then click Rename.
Type VendorInvoiceReport.
Right-click the Datasets node for the report, and then click Add Dataset.
Select the node for the dataset.
In the Properties window, specify the following property values.
Property
Value
Data Source
Dynamics AX
Data Source Type
Query
Name
InvoiceJournalDataset
Query
Click the ellipsis button (…). A dialog box displays where you can select a query that is defined in the AOT and identify the fields that you want to use. Select the InvoiceJournal query, and then select the DueDate, InvoiceAccount, InvoiceDate, InvoiceId, OrderAccount, and PurchId fields. Be sure the All check box is not marked.
In Model Editor, right-click the Datasets node for the report, and then click Add Dataset.
Select the node for the dataset.
In the Properties window, specify the following property values.
Property
Value
Data Source
Dynamics AX
Data Source Type
Query
Name
InvoiceTransactionDataset
Query
Click the ellipsis button (…). A dialog box displays where you can select a query that is defined in the AOT and identify the fields that you want to use. Select the InvoiceTransaction query, and then select the ItemId, LineAmount, Name, PurchPrice, and Qty fields. Be sure the All check box is not marked.
Since the queries that are used for both of the datasets have a range based on the InvoiceId field, parameters are added to the report in Model Editor. Parameters of this type are automatically added as soon as you bind the query to a dataset. The name of the parameter is derived from the dataset name and the field name. In this case, both parameters represent the same field. Therefore, you will set up the report so that one of the parameters is visible to the users and the other parameter is hidden. The hidden parameter will get its value from what the user enters for the visible parameter.

To configure the parameters

In Model Editor, expand the Parameters node.
Select the InvoiceJournalDataset_InvoiceId parameter.
In the Properties window, type Invoice ID: for the Prompt String property.
Select the InvoiceTransactionDataset_InvoiceId parameter.
In the Properties window, set the Visibility property to Hidden. Click the ellipsis button for the Values property. In the dialog box that displays, click the Parameter radio button, select the InvoiceJournalDataset_InvoiceId parameter from the drop-down menu, and then click OK.

To define a precision design using SQL Report Designer

In Model Editor, right-click the Designs node for the report, point to Add, and then click Precision Design.
The Precision Design window displays with an empty report. The Datasets window containing the datasets that you defined in the model appears on the left.
Note
If the Datasets window does not appear, a supported hotfix is available from Microsoft to fix this problem. To download the hotfix, see the MSDN Code Gallery for KB947173.
In the Toolbox pane, select the Textbox element and drag it to the upper-left side of the report.
Select the text box, and in the Properties window, set the Font property to Normal, Tahoma, 14pt, Normal. In the Value property, type Invoice specification. You may need to adjust the size of the text box.
In the Toolbox pane, select the Line element and draw a line below the text box that you added in the previous step.
Select the line, and in the Properties window, set the LineWidth property to 2pt and set LineColor property to Blue.
In the Toolbox pane, select the Table element and drag it below the line. Align the left side of the table with the beginning of the line.
Select the table, and in the Properties window, specify InvoiceJournalDataset for the DataSetName property.
Right-click the left column of the table and click Table Header so that it is not selected. Repeat and then click Table Footer so that it is not selected.
Right-click the left column of the detail row, and then click Insert Row Below. Repeat this until there are five detail rows in the table.
Right-click the right column of the table and click Delete Columns so that there are only two columns.
In the first cell of the first detail row, type Invoice account:.
Type text into the first cell of the remaining detail rows. The text that should be added is: Vendor account:, Purchase order:, Invoice date:, and Due date:.
In the Datasets window, select the InvoiceAccount field from InvoiceJournalDataset, and drag it to the second cell in the first detail row. Do the same for the cells in the remaining rows but use the OrderAccount, PurchId, InvoiceDate, and DueDate fields.
Select the second cell in both the fourth and fifth detail rows, and in the Properties window, type d for the Format property. This will format the values as dates.
Select the first column in the table, and in the Properties window, set the Font property to Normal, Tahoma, 10pt, Bold.
Select the second column in the table, and in the Properties window, set the Font property to Normal, Tahoma, 10pt, Normal, and set the TextAlign property to Left.
In the Toolbox pane, select the Table element, and drag it below the previous table.
Select the table, and in the Properties window, set the BackgroundColor to Lavender, and set the DataSetName property to InvoiceTransactionDataset.
Right-click the left column of the header row and then click Insert Row Above. Right-click the left column of the footer row and then click Insert Row Below, and add columns to the table so that it contains a total of five columns. You may need to resize the column widths.
Select all the cells in the first header row, right-click the selection, and then click Merge Cells.
Select the merged cell, and in the Properties window, set the Font property to Normal, Tahoma, 10pt, Bold, set the TextAlign property to Center, and type Item details for the Value property.
Select both the last header row and the details row, and in the Properties window, set the BorderColor property to DarkGrey, set the BorderStyle property to Solid, and set the TextAlign property to Center.
In the second header row, type the following headings in the cells: Item, Description, Quantity, Unit price, and Amount. In the Properties window, set the Font property for each of these cells to Italic, Tahoma, 10pt, Normal.
Drag the ItemId, Name, Qty, PurchPrice, and LineAmount fields from InvoiceTransactionDataset in the Datasets window to the appropriate cells in the details row below the headings that you just created. The cell should display the value of the field. For example, the expression of the first cell in the details row should be =Fields!ItemId.Value. In the Properties window, set the FontFamily property for each of these cells to Tahoma.
Select the cells in the details row that display the values for unit price and amount, and in the Properties window, type c for the Format field. This will format the values in these cells as currency.
In the first footer row, merge the first four cells.
Select the merged cell, and in the Properties window, set the FontFamily property to Tahoma, set the TextAlign property to Right, and type Sales tax: for the Value property.
Select the last cell in the first footer row, type =Sum(Fields!LineAmount.Value*.07) for the Value property, set the FontFamily property to Tahoma, and type c for the Format property.
In the last footer row, merge the first four cells.
Select the merged cell, and in the Properties window, set the FontFamily property to Tahoma, set the FontWeight property to Bold, set the TextAlign property to Right, and type Total amount due: for the Value property.
Select the last cell in the last footer row, type =Sum(Fields!LineAmount.Value*1.07) for the Value property, set the Font property to Normal, Tahoma, 10pt, Bold, and type c for the Format property.
Select the cells that display the values for sales tax and total amount due, and in the Properties window, set the BorderColor property to DarkGrey, set the BorderStyle property to Solid and set the TextAlign property to Center.
Save the report.
To preview the report design, click the Preview tab in SQL Report Designer. Type an invoice ID in the Parameters tab, and then click the Report tab to view the report.