AX/365 F&O Development learning and sharing

Overview There are multiple methods to develop SSRS reports in Microsoft Dynamics AX 2012. This tutorial will guide you in developing Report Data Provider (RDP) based SSRS reports. RDP based SSRS Reports are used when complex business logic cannot be achieved using AOT query. Pre-requisites Microsoft Dynamics AX 2012 Visual studio 2012 SQL Server Reporting Services (SSRS) must be configured Reporting services extensions must be installed in Dynamics AX Important Concepts Report Data Provider (RDP) Class Report Data Provider Class is an X++ class that is used to access and process data for an SSRS report. The RDP class processes the business logic based on a specified parameter and/or query and returns a dataset to the reporting services. In order to create an RDP class in AX, you have to extend that class with  SRSReportDataProviderBase . This tells AX that this class will be used by reporting services to process the data. Two important attributes are use...

How to update customer address using Code static   void  updateCustomerAddress(Args _args) {     LogisticsPostalAddress      address;     CustTable                   custtable;     DirPartyPostalAddressView   postaladdressView;     DirParty                    dirparty;     LogisticsLocation           location;     DirPartyTable               dirPartyTable;          while   select  custtable  where  custtable.AccountNum  == "100"        ...

Data Bases in Ax There are three database components:  Transaction DataBase Model Store BaseLine Model Store The Application Object Server (AOS) connects to the Microsoft Dynamics AX database to process transactions.  The AOS connects to the model store to display forms and reports.  The baseline model store is used to upgrade X++ code to Microsoft Dynamics AX 2012, and to analyze application updates before they are applied. In Microsoft Dynamics AX 2012 R3 and Microsoft Dynamics AX 2012 R2, the model store and the transaction data are stored in separate databases.  In earlier versions of Microsoft Dynamics AX 2012, the model store and transaction data are stored in a single database.

My build/release process is almost entirely automated, except for one step, where we refresh the WSDL/WCF configuration.  So far, I've only been able to do it conventionally with the mouse. I wrote a little command line tool in C# that you can incorporate into your build scripts that should refresh your WCF configuration in your AXC file automatically. It has one dependency on the AX client configuration tool obviously, which is located at: C:\Program Files\Microsoft Dynamics AX\60\BusinessConnector\Bin\AxCliCfg.exe Usage: RefreshAXCConfig.exe <axc file> <aos name> <WSDL Port> Example: RefreshAXCConfig.exe C:\CUS.axc DevAOS 8101 The C# code is simple below, and make sure to add the reference to AxCliCfg.exe.  using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Text.RegularExpressions; using System.IO; using System.Xml; using Microsoft.Dynamics.Configuration; namespace R...

Job for updating the Vendor account and update PO  static void updatePO_VendorAccount(Args _args) {     PurchTable po;     PurchLine pl;     VendTable vT;     VendPackingSlipJour vendP;     PurchId poNum;     DialogField dpo;     VendAccount vendor;     DialogField dvendor;     Dialog d;     d = new Dialog();     d.caption("Choose a PO to update and the vendor account");     dpo = d.addField(extendedTypeStr(PurchId));     dvendor = d.addField(extendedTypeStr(VendAccount));     d.run();     poNum = dpo.value();     vendor = dvendor.value();     if(d.closedOk() && poNum && vendor && Box::yesNo(strFmt("You are about to update      PO: %1 to Vendor: %2. Do you wish to continue?", poNum, vendor), DialogButton::No)) { ...

This summary is not available. Please click here to view the post.