Add Lookup to Batch Job Dialog in Ax 2012


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:
Untitled
We’ll be adding a new UI Builder class MAKSalesTableUIBuilder and link it with the MAKSalesTableContract class to add lookup on the batch dialog. It is highly recommended to read the prerequisites first before proceeding any further to have better understanding of the topic.
Development steps:
1. Add salesChannel variable to the class declaration of MAKSalesTableContract class to store sales channel value:
[DataContractAttribute]
class MAKSalesTableContract
{
    TransDate           fromDate;
    TransDate           toDate;
    MAKSalesChannel     salesChannel;
}
2. Add parm method for sales channel variable to designate it as a data member of the contract class:
[
    DataMemberAttribute,
    SysOperationLabelAttribute(literalStr("Sales channel")),
    SysOperationHelpTextAttribute(literalStr("Pick sales channel")),
    SysOperationDisplayOrderAttribute('3')
]
public MAKSalesChannel parmSalesChannel(MAKSalesChannel _salesChannel = salesChannel)
{
    salesChannel = _salesChannel;

    return salesChannel;
}
3. Compile and generate incremental CIL.
4. Click Tools > Caches > Refresh elements to refresh the AOD cache to reflect changes on the batch dialog.
5. You should be able to see newly added Sales channel field on the batch dialog but without a lookup.
Untitled
6. Create a new class MAKSalesTableUIBuilder which extends SysOperationAutomaticUIBuilder base class:
class MAKSalesTableUIBuilder extends SysOperationAutomaticUIBuilder
{
    #define.lookupAlways(2)

    DialogField     fromDateField;
    DialogField     toDateField;
    DialogField     salesChannelField;
}
7. Override the postBuild method of the base class to get the references to dialog field controls after creation:
public void postBuild()
{
    super();

    //Get references to dialog controls after creation
    fromDateField = this.bindInfo().getDialogField(
        this.dataContractObject(), methodStr(MAKSalesTableContract, parmFromDate));
   
    toDateField = this.bindInfo().getDialogField(
        this.dataContractObject(), methodStr(MAKSalesTableContract, parmToDate));
   
    salesChannelField = this.bindInfo().getDialogField(
        this.dataContractObject(), methodStr(MAKSalesTableContract, parmSalesChannel));

    //Change text field metadata to add lookup
    salesChannelField.lookupButton(#lookupAlways);
}
8. Override the postRun method of the base class to register the custom lookup method salesChannelFieldLookup with the form control event lookup:
public void postRun()
{
    super();

    //Register overrides for form control events
    salesChannelField.registerOverrideMethod(
        methodstr(FormStringControl, lookup),
        methodstr(MAKSalesTableUIBuilder, salesChannelFieldLookup),
        this);
}
9. Give the following implementation for the custom lookup method salesChannelFieldLookup:
public void salesChannelFieldLookup(FormStringControl _control)
{
    Query                   query;
    QueryBuildDataSource    qbdsMAKSalesTable;
    SysTableLookup          sysTableLookup;

    query = new Query();
    qbdsMAKSalesTable = query.addDataSource(tableNum(MAKSalesTable));
    qbdsMAKSalesTable.fields().clearFieldList();
    qbdsMAKSalesTable.fields().addField(fieldNum(MAKSalesTable, SalesChannel));
    qbdsMAKSalesTable.addGroupByField(fieldNum(MAKSalesTable, SalesChannel));

    sysTableLookup = SysTableLookup::newParameters(tableNum(MAKSalesTable), _control);
    sysTableLookup.addLookupfield(fieldNum(MAKSalesTable, SalesChannel));
    sysTableLookup.parmQuery(query);
    sysTableLookup.performFormLookup();
}
10. Lastly, modify the class declaration of MAKSalesTableContract class to link it with the MAKSalesTableUIBuilderclass we just created by decorating it with the SysOperationContractProcessingAttribute:
[
    DataContractAttribute,
    SysOperationContractProcessingAttribute(classStr(MAKSalesTableUIBuilder))
]
class MAKSalesTableContract
{
    TransDate           fromDate;
    TransDate           toDate;
    MAKSalesChannel     salesChannel;
}
11. Compile and generate incremental CIL.
12. Click Tools > Caches > Refresh elements to refresh the AOD cache to reflect changes on the batch dialog.
13. Click on the menu item MAKSalesTableService to run the batch job dialog.
14. You should now be getting a lookup generated for the Sales channel field on the batch dialog





Customize Controller for Batch Job

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 of what we have done so far in the Batch Framework series.
Business Requirement:
To set batch dialog fields with default values.
Project Overview:
Untitled
Development Steps:
1. Create a new class MAKSalesTableServiceController extending SysOperationServiceController base class.
class MAKSalesTableServiceController extends SysOperationServiceController
{
}
2. Override the new method and give the following definition:
public void new()
{
    super();
 
    this.parmClassName(classStr(MAKSalesTableService));
    this.parmMethodName(methodStr(MAKSalesTableService, processRecords));
}
3. Create a new method main and give the following definition. This is where the magic happens. The controller is used to get reference to data contract object which is then modified to initialize data members, by calling their parm methods, with default values.
static void main(Args _args)
{
    MAKSalesTableServiceController  controller;
    MAKSalesTableContract           dataContract;
 
    controller = new MAKSalesTableServiceController();
 
    // Run operation synchronously, asynchronously or in batch
    // Async execution requires service to be published
    // in the AxClient service group
    controller.parmExecutionMode(SysOperationExecutionMode::ReliableAsynchronous);
 
    // Get the contract from the controller and initialize it default values
    dataContract = controller.getDataContractObject();
    dataContract.parmFromDate(systemDateGet());
    dataContract.parmToDate(systemDateGet());
    dataContract.parmSalesChannel("Direct");
 
    // call the operation. The controller will handle execution mode
    controller.startOperation();
}
4. Modify Menu Items > Action > MAKSalesTableService to point to MAKSalesTableServiceController class just created.
Untitled
5. Compile and generate incremental CIL.
6. Click Tools > Caches > Refresh elements to refresh the AOD cache to reflect changes on the batch dialog.
7. Click Menu Items > Action > MAKSalesTableService to run the batch job.
8. You should now be getting batch dialog fields initialized with default values
Untitled


Comments

Post a Comment

Popular posts from this blog

Table Methods in Ax 2012

Table Methods in Ax 2012 Methods are used for adding X++ code to your application. The code in methods is also referred to as business logic. Whenever records are changed, inserted or deleted from a table various default methods are executed. We can change the default methods and by doing so we are overriding the default methods.To override a method go to the  Methods  node of a table, right click and choose  Override Method . Below are few examples of Overriding commonly used Table methods: initValue(): If we create a new record from the table browser or a form the table method initValue() is executed. It is used to set a default value for the fields.  Example (1): Let’s override intiValue for MyFirstTable and set default value for custGroupId public void initValue() { super(); this.custGroupId = "10"; } After adding this method, open table MyFirstTable  through Table browser and press ctrl+n to create a new record. The field custGroupId wil
Read more

Write/ Read to Excel Sheet

File exists in a Directory:  static void FileExists(Args _args) { str filePath = @”C:\\vani.pdf”; ; if(WinAPI::fileExists(filePath)) { WinAPI::copyFile(filePath,”C:\\1.pdf”); } } Dynamics AX X++ code to Read/Write data to excel Writing Data to Excel file   How it works 1. Use SysExcelApplication class to create excel file. 2. Use SysExcelWorkbooks and SysExcelWorkbook to create a blank workbook(by default 3 worksheets will be available). 3. Use SysExcelWorkSheets to select worksheet for writing data. 4. SysExcelCells to select the cells in the excel for writing the data. 5. SysExcelCell to write the data in the selected cells. 6. Once you done with write operation use SysExcelApplication.visible to open file. static void Write2ExcelFile(Args _args) { InventTable inventTable; SysExcelApplication application; SysExcelWorkbooks workbooks; SysExcelWorkbook workbook; SysExcelWorksheets worksheets; SysExcelWorksheet worksheet; SysExcelC
Read more

Financial Dimensions in AX 2012

Image
Today we will be exploring the new changes  related  to Financial dimensions in AX 2012. Earlier versions AX 2009, 4.0 : Ø   In older version System use to limit the creation of dimensions up to 10.  Ø   By default 3 dimensions were available in the system namely Department, CostCenter and Purpose. Ø   Technically these dimensions were controlled by Enum SysDimension and an array EDT Dimension. Ø   So If we have 3 enum elements in SysDimension, then its corresponding array elements are stored in    dimension EDT and can be referred as Dimension[0], Dimension[1]..... Ø   If you would like to store these dimension values against customized table, then simply we were adding the EDT Dimension to that Table. At  Form  level simply drag and drop field on Group then system use to  show all the array elements as string control. New version AX 2012 (6.0) :   Ø   In AX 2012(6.0), there is no limit to dimension creations. One can create n number of dimensions as per orga
Read more