The purpose of this document is to demonstrate what power we can leverage by customizing the controller for our batch job. For simplicity, we’ll explore how we can set batch dialog fields with default values by extending SysOperationServiceController class. Prerequisites: It is highly recommended to go through the following posts to get a better understanding […]
Prerequisites: 1. Create a simple batch job. 2. Add fields to batch job dialog. Business Requirement: To have a lookup on the batch job dialog to filter records to be processed based on the user selected value of sales channel field on the dialog. Project Overview: We’ll be adding a new UI Builder class MAKSalesTableUIBuilder and
Prerequisites: 1. Create a simple batch job. Requirement: To add custom fields to batch job dialog to choose a date range to process only those records falling in that date range. Project overview: As you can see in the picture, a data contract class MAKSalesTableContract has been added to the project to achieve the goal.
Please follow the instructions below to switch the TFS branch of the Dynamics AX development environment. Add user to Administrators group using an admin account. Add user to AX Debugging users group using an admin account. Create new login for the user to SQL Server > Security node. Disconnect AX from TFS. Disable version control.
In this post we’ll learn how to create a very basic custom Batch job using SysOperation framework. We’ll use the base controller class SysOperationServiceController and develop a custom service operation class to achieve the goal. Requirement: To create a Batch job to mark all the records as processed in a custom table MAKSalesTable. Project overview: The
Another masterpiece, Microsoft Dynamics AX 2012 R3 Reporting Cookbook by Packt Publishing, is out in the market for those who want to become gurus of SSRS Reporting for Dynamics AX. I had a chance to technically review the book to ensure that it offers the best and accurate technical content possible. It is a MUST read and I
Download it, adapt it, run it! [office src=”https://onedrive.live.com/embed?cid=2773BC7CE682FCFA&resid=2773BC7CE682FCFA%21122&authkey=AO_2C8pUPpdoT6E” width=”98″ height=”120″] Please find above the project XPO of the Off-the-shelf Excel reader. To adapt and run it for your Excel file format: Update macros in the class declaration to match your Excel file columns. Update readExcelFile() method to use your table buffer to persist records
To set Label property of all the fields of a table in AOT, you may refer to the following code which loops through all the fields of a table and sets their Label property with their Name property. static void MAKSetLabels(Args _args) { #Properties SysDictTable dictTable = new SysDictTable(tableNum(CustTable)); SysDictField dictField; TreeNode treeNode; FieldId fieldId
It is often a customer requirement to check for custom validations before posting a Sales Order. The best place to put your code for custom validations can be found below: Validations for Sales Table: AOT > Classes > SalesFormLetterProvider > checkHeading() For example, To check for custom field SalesTable.MAKBlocked, this is how custom validation should be added in
Challenge: What if you need to integrate a Retail E-Commerce website with the powerful Dynamics AX ERP at backend to leverage numerous functional capabilities it offers in the areas like but not limited to Supply Chain Management. Then you are reading the right blog post! We can achieve it through exposing custom AIF services as web services on IIS using