Technical Tutorials on MS Dynamics Axapta 2012,D365 FnO

To  perform spell checking in ax write following code SysSpellChecker spailingch = SysSpellChecker::newLanguageId('en-us'); ; info(strfmt('%1', spailingch.checkSpelling("Problems"))); info(strfmt('%1', spailingch.checkSpelling("preoblams")));

How to Show Alert message on axapta startup If you want to show any ax client startup alert then you can put code following way Open AOT (Ctrl+D) then Go to Info Class Write following code on StartupPost() Method void startupPost() { ; box::info("Welcome to Microsoft dynamics axapta Application"); }

 The domain account the SQL Server Analysis Services (MSSQLSERVER) Windows service will run as. When installing Analysis Services, specify that the Analysis Services Windows service should run as the .NET Business Connector account. The .NET Business Connector account must have read access to the Microsoft Dynamics AX online transaction processing (OLTP) database.

On the SSRS server machine where you have .NET BC installed, check the following:  Check Microsoft.Dynamics.BusinessConnectorNet file version in :\windows\assembly folder (GAC). To do this, right-click on the file, select Properties then select the Version tab. Make sure it's the same version as your AOS version (ax32serv.exe) Make sure that the SSRS service account is the same as your Business Connector Proxy account in Dynamics AX. Check the Dynamics AX client configuration for the Business Connector (non-interactive use only) configuration and make sure it points to an active AOS in the Connection tab. (Administrative Tools> Microsoft Dynamics AX 2009 Configuration) Copy the Business Connector configuration to the desktop and double click on it to launch Dynamics AX. This will validate that the configuration is good Check the Application event log on the SSRS server to make sure you do not see other errors as to why Business Connector is not able to c...

How to extract all the AOT modifiaction in axapta Create a new project, then click (CTRL+F3 or Advanced Filter/ sort) >> then Grouping(AOT) > then SELECT >> in the LAYER field put >>usr>> in the criteria filed >> then OK Also there is an additional way  to do it easily.  going to the AOT > right click --> Export(Tick) -> Aplication Object layer Choose -> USR layer->OK  

AxLookup is used in data entry pages to help the user select a valid value for a field that references keys from other tables. In Enterprise Portal, lookups are metadata-driven by default, and they are automatically enabled for fields, based on the relationship that is defined in metadata in the AOT. An example is the customer group lookup on the customer creation page. The extended data type (EDT) and table relationship metadata in the AOT define a relationship between the customer table and the customer group table; therefore, a lookup is rendered so that the user can select a customer group in the customer group field when creating a customer record. You don’t need to write any code to enable this behavior—it happens automatically. void dataSetLookup(SysDataSetLookup sysDataSetLookup) { if (custTable.CountryRegionId) { sysDataSetLookup.parmQuery().dataSourceNo(1).addRange( fieldnum(AddressZipCode,CountryRegionId)).value(queryValue(custTable.CountryRegionId)); } ...

Example of Getting the bound field value in Enterprise portal static AxBoundField GetField(DataControlFieldCollection fields, string name) { foreach (DataControlField field in fields) { AxBoundField boundField = field as AxBoundField; if (boundField != null && String.Compare(boundField.DataField, name, true) == 0) return boundField; } return null; } AxBoundField parentCaseId = (AxBoundField)GetField(this.GeneralRight.Fields, "editParentCaseId**");