Simple List & Details Form- Designing with Screen shots

we add our form design. Here you will learn the Dynamics AX way of dealing with fundamental components like tabs, lists, containers, details, and grids. You’ll even do some minor customization to the action menu. While the tutorial has been made purposely simple for introductory learning, it’s a great start to learning the Dynamics AX way.
Scenario: Your users want to be able to view multiple records in a table and edit them at the same time. Enter our hero, the simple list and details form.
What You Need: In order to do this demonstration, you need the free Dynamics AX 2012r2 image provided by Microsoft and on Partner Source. You will also need to have completed Part 1 of this series.

  1. Within the SimpleListDetailExample project, expand the Designs node and right click on theDesign node. Select Properties. The Design (not Designs) sub-node is where we do the majority of our form layout design. While we can do drag and drop in MorphX like a .NET Windows development tool, the preferred way is to add things to the Design node in the way that I will be displaying here. This is because MorphX is very good at positioning controls for us. Learn to accept the benefits of automatic behaviors within MorphX. It will make things easier to just let the tool do what it does best. 



  2. In the properties box, change the DataSource Property to CustTable. Change theTitleDataSource property to CustTable. Setting the DataSource property is required as this is how you map your design to the actual data. Setting the Title Data Source is highly recommended except for 3 cases, one of them here. You can leave this property alone onSimpleList, SimpleList and Details, or a Table of Contents template. The Title Data source just makes the table name appear as a label followed by a dash like this: [Customers – Customer Account: 4010, The Lamp Shop]. 


  3. Now, think of the action Pane like the ribbon. It’s a panel of menu options. In Dynamics AX, map your Action Pane to a data source and it will auto-populate menu options for you. Of course, this can be customized but this auto behavior is really cool.
    Right-click on the ActionPane, left-click on Properties. Set the DataSource to CustTable.


  4. Now, to make this easier, we will need another development window open. More specifically, we’ll need one showing the forms window. If it isn’t already open, right-click onDemoListDetailForm within your SimpleListDetailsExample project window, and select Open in New Window. At any rate, you should have two windows looking like this:


  5. Using drag and drop by highlighting fields and using the mouse, drag the following fields from Data Sources/Fields over to the [Grid:Grid](usr). You will do this by dropping the fields on the[Grid:Grid](usr). The following fields need to be added:
    Party, AccountNum, SalesGroup, and CashDisc. Adding 2 fields here is best but anything less than 4 is okay. The idea is to keep the number of fields short because you just want to show the user what is necessary to identify the row. They will be able to look to the right to get the details for each row.


  6. Right-Click on [Grid:Grid](usr), select Properties, and change the MultiSelect property to No.Make sure that the DataSource property is set to CustTable. This will map the grid to the right table and also prevent users from selecting more than one row at a time for editing.
  7. Right-Click on [Group:Body](usr) and choose Properties. Change the Style property toSplitterVerticalContainer. 


  8. Expand the Design node, expand the [Group:Body](usr), expand the [Tab:DetailsTab](usr)group. In the property sheet for the tab control, click the Style property, and then select Tabs for the property. This means that you expect all of the fields to fit on one page which means that there aren’t many fields. 


  9. Expand the [Tab:DetailsTab](usr) and then click the tab page with the [TabPage:TabPage](usr).Click the properties option and set the Caption property to Our Example Property. Now, you will be able to see a caption in the form when it runs. 

  10. Now drag the Dimension folder and the Delivery folder over to the [TabPage:TabPage](usr). Note: the dimension folder and Delivery folder are known as field groups. Field groups are related fields that often go together. They are often enclosed by a square so that the user logically knows that these columns are related in some sort of way. A good practice is to define field groups because it makes it much faster to build forms. 
    Then, click the save all option. Afterwards, compile your project and run it.


  11. And finally, let’s see how everything looks. Right-Click on the DemoListDetailForm and clickOpen to preview the form.



Comments

Post a Comment

Popular posts from this blog

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 workshee...
Read more

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 ...
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 ...
Read more