Posts

Showing posts from August, 2018

While doing ProductReceiptList, DocumentNum field added, and need to display that field in ProductReceiptJournal form

While doing ProductReceiptList, DocumentNum field added, and need to display that field in ProductReceiptJournal form : Step 1: Need to add new "DocumentNum" field in "VendPackingSlipJour" Table. Step 2: Added Code in "PurchpackingSlipJournalCreate" Class -> initHeader( )             vendPackingSlipJour.DocumentNum           = purchParmTable.DocumentNum; Step 3: Need to do "Increment CIL", if data is not effected.

PurchaseInvoice Report

Purchase Invoice Report: Contract Class: [ DataContractAttribute] public class INC_PurchaseInvoiceContract {     VendInvoiceId           vendinvoiceId; } ------------------------- [DataMemberAttribute("VendInvocieId")] public VendInvoiceId parmVendInvoiceId(VendInvoiceId _vendinvoiceId = vendinvoiceId) {     vendinvoiceId = _vendinvoiceId;     return vendinvoiceId; } --------------------------------- RDP Class: [SRSReportParameterAttribute(classstr(INC_PurchaseInvoiceContract))] public class INC_PurchaseInvoiceDP extends SrsReportDataProviderPreProcessTempDB {     INC_PurchaseInvoiceContract         contract;     INC_PurchaseInvoiceHeaderTmp        header;     INC_PurchaseInvoiceLineTmp          lines;     VendInvoiceId                    ...

Based on output menuitem by using "DocumentStatus" in SalesEditLines form

While selecting PackingSlip in SO Process, Need to do mandatory fields(DriverId,TruckId) of ParmSalesTable, Based on output menuitem, which we cannot do, so another way by using "DocumentStatus". IN SalesEditLines Form -> Init( )  if(documentStatus == DocumentStatus::PackingSlip)     {         SalesParmTable_INC_DriverId1.mandatory(true);         SalesParmTable_INC_TruckId1.mandatory(true);     }     else     {         SalesParmTable_INC_DriverId1.mandatory(false);         SalesParmTable_INC_TruckId1.mandatory(false);     }

need to get WareHouse lookup based on "ItemType", which needs to match InventLocation "ItemType"

While creating SalesOrder, need to get WareHouse lookup based on "ItemType", which needs to match InventLocation "ItemType" step 1: Add new field in "InventLocation" Table and drag field in particular form level. Step 2: In SalesCreateOrder form -> Datasource -> SalesTable -> Fields -> InventLocationId -> Lookup( )         public void lookup(FormControl _formControl, str _filterStr)        {             SysTableLookup          sysTableLookup = SysTableLookup::newParameters(tableNum(InventLocation),_formControl);          Query                   query = new Query();          QueryBuildDataSource    queryBuildDataSource = query.addDataSource(tableNum(InventLocation));             queryBuildDataSource.addRange(fieldNum(InventLo...

Need to provide “ItemId lookup” based on "ItemType" field, which selected while creating SalesOrder

In SalesTable form – Need to provide “ItemId lookup” based on "ItemType" field,  which selected while creating SalesOrder In SalesTable Form -> Datasource -> Salesines -> Fields -> ItemID -> Lookup( )     SysTableLookup          sysTableLookup = SysTableLookup::newParameters(tableNum(InventTable),_formControl);     Query                   query = new Query();     QueryBuildDataSource    queryBuildDataSource = query.addDataSource(tableNum(InventTable));         queryBuildDataSource.addRange(fieldNum(InventTable, ItemType)).value(queryValue(salesTable.ItemType));     sysTableLookup.addLookupfield(fieldNum(InventTable,ItemId));     sysTableLookup.addLookupMethod(tableMethodStr(InventTable,defaultProductName));     sysTableLookup.addLookupMethod(tableMethodStr(InventTable,itemGroupId));   ...

We will follow the following steps in the AX development.

We will follow the following steps in the AX development. 1. Follow the naming convention: - All new objects will start with a prefix ‘INC_ModuleNameofObject’ - Adding a new field to an existing table should be prefixed with ‘INC_ModuleNameofObject’ - Created Extended Data Types for any new fields you create. - Follow the rest of the standard processes for methods, relations, indexes, delete actions. 2. Label file: - Create a new label file or use an existing for your customization. - Label file will have the 1st 3 digits of the Customer Name (Functional consultant can help         to identify the names.) 3. Please maintain a XPO for the customization, we will use it for the deployment.         Please maintain a backup and forward it to me end of the day. 4. The customization will be done on the test environment. It will be tested by the functional consultant         and then by the end user. ...