Microsoft Dynamics AX

Changing Layer in Dynamics AX 2012: 1.        Click Start, point to Administrative Tools, and then click Microsoft Dynamics AX 2012 Configuration. The Microsoft Dynamics AX Configuration Utility opens. In the Microsoft Dynamics AX Configuration Utility, click Manage, and then click Create configuration. The Create Configuration window opens In the Configuration name field, enter a name for the configuration, and then click OK. The Create Configuration window closes On the Developer tab, in the Application object layer to open field, select a new layer from the drop-down list. On the Developer tab, in the Application object layer to open field, select a new layer from the drop-down list.     In the Development license code field type the license code and  confirm license field also give the same   Click Apply and  Click OK to save the configuration. The Microsoft Dynamics AX Configura...

When ever we face a problem for a specific user in AX 2009 or 2012. We have to delete *.auc files then the problem may resolve. I  am going to mention how to delete the files kindly follow below 3 points and check. 1. Stop AOS. 2. Delete the *.auc files from users\\Appdata\ folder 3. Restart AOS.

MorphX   MorphX is the Microsoft Dynamics AX IDE( Integrated Development Environment) which includes:  - Data Dictionary  - Tools for creating menus, forms and reports for Windows- and Web clients  - Compiler and debugger for the object oriented programming language X++  - Version control system  - Label (multi language text) systems  : IntelliMorph  IntelliMorph is the Runtime Environment embedded in Microsoft Dynamics AX, that draws menus, forms, and reports for Windows- and Web-clients with the correct contents, size, and layout according to:  - The language your texts are displayed in.  - What features you can access.  - How wide you want the fields on your installation.  - The formats you are using for dates and numbers.

What are Integration ports? Integrations ports are basically the inbound or outbound ports through which external applications can communicate with Dynamics AOS via AIF (WCF). The exchange of data between External/Internal application is divided into: 1.        InBound Exchange a.       Both Basic and Enhanced Integration ports can be used. b.       Basically to Receive data and create in Ax 2.       OutBound Exchange a.       Only Enhanced Integration ports can be used. b.       To Send data to ext. applications c.        To Send data to ext. applications in response to their Requests   How to: Create a Basic Inbound Integration Port [AX 2012] Basic port is used to test the operation of a custom service that does not require any data processing or exposure to the Internet. O...

While working, I encountered this error. The error is mentioned in the image below: And the compilation log had the following error: I was able to solve the error by carrying out the outlined steps: 1.Restart AOS Service 2.Generate Full CIL In case, you do not have enough time for the Full compilation, go the error log and recompile the objects mentioned in the error message.

The job “CustomerForm” creates a customer form at run time in x++. In the form, I have used two datasources “CustTable” and “DirPartyTable”. I have also shown how to add menuitemfunctions in a form through X++. Here is the code in X++: public static void CustomerForm(Args _args) { //Initialization DictTable dictTable; DictTable dictTable1; Form form; FormBuildDesign design; FormBuildDataSource formBuildDataSource; FormBuildDataSource formBuildDataSource1; FormBuildActionPaneControl actionPane; FormBuildActionPaneTabControl actionPaneTab; FormBuildButtonGroupControl buttonGroup1; FormBuildButtonGroupControl buttonGroup2; FormBuildCommandButtonControl CommandNew; FormBuildCommandButtonControl CommandDelete; FormBuildMenuButtonControl CustomerButton; FormBuildFunctionButtonControl NewCustomerButton; FormBuildFunctionButtonControl ForecastButton; FormBuildGroupControl Grp; FormBuildGridControl grid; FormBuildGroupControl grpBody; Args args; FormRun formRun; #task //Adding DataSourc...

Previously, the Runbase framework was being used to add the functionality that required batch processing. The Runbase framework has been replaced by the SysOperation framework, formerly known as Business Operation Framework. The Sysoperation framework creates a user interface which can be integrated with the batch server for batch processing. The SysOperation framework can be used to implement operations that can scale to multiple processors by batch processing. It can also be implemented to prompt the user for an input. The batch processing feature can be used to control the time and duration of the operations which require more processing time. The framework also has support for queries, routing tasks and pack and unpack for parameter serialization. The SysOperation framework basically enhances the performance of operations by explicitly scheduling their execution. Through the framework, the operations can be executed on user interaction or by scheduling them through the batch s...

Microsoft Dynamics AX 2012 Xpp – Sales Orders Import Microsoft Dynamics AX 2012 Xpp – Sales Orders Import   Purpose:  The purpose of this document is to illustrate how to write a required minimum X++ code in Microsoft Dynamics AX 2012 in order to import Sales orders.   Challenge : Data model changes in Microsoft Dynamics AX 2012 related to high normalization and introduction of surrogate keys made some imports more complex. However the structure of tables comprising Sales order header/lines didn't change. Please note that after you import Sales orders you may need to perform full/partial Physical and/or Financial update if required (for example, for Purchase orders already in execution).   Solution : Appropriate tables buffers (SalesTable, SalesLine) will be used when writing X++ code in Microsoft Dynamics AX 2012 in order to import Sales orders. Alternatively AxBC classes may be used instead of table buffers.   Data Model :  ...

lookup for custaccount field, when open the custtable (custaccount field)  form public void lookup() { Query query = new Query(); QueryBuildDataSource qbds_CustTable; SysTableLookup sysTableLookup; QueryBuildRange qbr; //super(); sysTableLookup = SysTableLookup::newParameters(tablenum(CustTable), this); qbds_CustTable = query.addDataSource(tableNum(CustTable)); sysTableLookup.addLookupfield(fieldnum(CustTable, AccountNum), true); sysTableLookup.addLookupfield(fieldnum(CustTable, CustGroup),true); qbr = qbds_CustTable.addRange(fieldNum(CustTable,CustGroup)); qbr.value(‘ENDUSER’); sysTableLookup.parmUseLookupValue(false); sysTableLookup.parmQuery(query); sysTableLookup.performFormLookup(); } About these ads