Skip to main content

🚀 How to Dynamically Copy Matching Fields Between Tables in X++ using DictTable

 In Microsoft Dynamics AX (X++), there are many scenarios where you need to duplicate data from one table to another—especially during custom import, duplication, or versioning processes. Traditionally, this is done by manually assigning each field: targetTable.Field1 = sourceTable.Field1; targetTable.Field2 = sourceTable.Field2; ... But what if the tables have many fields ? Or maybe you’re dealing with multiple similar table pairs? That’s where the powerful DictTable class comes in. Let’s walk through how to use it to copy matching fields dynamically between two tables. 💡 Use Case: Copy Customer Templates Let’s assume you have these tables: CustTemplateHeader – stores predefined customer templates. CustTemplateHeaderHistory – a historical copy of templates for versioning. You want to copy records from CustTemplateHeader to CustTemplateHeaderHistory , but only for fields that exist in both tables. ✅ The Solution Using DictTable SalesHeaderTemplate   ...

Sorting Data in X++ (D365FO) Grids Using Form Data Source Events

 Introduction: In Dynamics 365 Finance and Operations, form grids often display data retrieved from a table or query. However, the default sorting applied may not always align with business requirements. Customizing sorting behavior at runtime ensures that the grid data is presented in a meaningful order for users.

This blog post demonstrates how to use the Initialized event of a form data source to apply custom sorting to a grid. We will sort the grid rows based on a specific field (DisplayOrder) in ascending order.


Understanding the Code:

Here’s the complete code snippet:

---------------------------------------------------------------------------------------------------------------

[FormDataSourceEventHandler(formDataSourceStr(MyFormDataSource,  MyTable), FormDataSourceEventType::Initialized)]

public static void MyFormDataSource_OnInitialized(FormDataSource sender, FormDataSourceEventArgs e)

{

    // It will clear if any other sorting is applied on the grid

    sender.queryBuildDataSource().sortClear();


    // It will add the sorting on the field

    // Use the table and field as per your own requirement in fieldNum function.

    // Use the ascending or descending order as per your own requirement

    sender.queryBuildDataSource().addSortField(fieldNum(MyFormDataSource, DisplayOrder), SortOrder::Ascending);

}

--------------------------------------------------------------------------------------------------------------------

Step 1: Registering the Event Handler

The [FormDataSourceEventHandler] attribute links the method to the Initialized event of the form data source. In this example, the MyFormDataSource data source is targeted. This event is ideal for modifying query behavior before data retrieval.

Step 2: Clearing Existing Sorting

The sortClear() method removes all previously applied sorting criteria from the query. This ensures that only your custom sorting is applied.

Step 3: Applying Custom Sorting

The addSortField method applies sorting to the DisplayOrder field. You can customize the field and sort order (ascending or descending) based on your requirements.


Use Case: Imagine a grid that displays a list of tasks or items. If you want the rows to appear in the order of priority or any other logical sequence defined by a DisplayOrder field, this event handler ensures the sorting is applied automatically whenever the form loads.


Advantages:

  • Consistency: Ensures the grid always displays data in the desired order.
  • User-Friendly: Reduces the need for users to manually sort the data.
  • Dynamic Behavior: Sorting logic is applied programmatically, making it easier to adapt to changing requirements.

Conclusion: Customizing grid sorting in D365FO is a powerful way to enhance user experience. By leveraging the Initialized event of the form data source, you can programmatically control how data is presented in the grid. Try this approach in your forms to make data presentation more intuitive and aligned with business needs.

Let us know in the comments if you found this tutorial helpful or if you have any questions! 😊



Comments

Popular posts from this blog

How to Refresh a Form or Data Source in D365FO Using X++

  Introduction In Microsoft Dynamics 365 Finance & Operations (D365FO), refreshing the form after an action (like inserting, updating, or deleting a record) is essential for keeping the UI updated with the latest data. In this blog, we’ll explore two ways to refresh the form in X++: ✅ Refreshing the entire form using taskRefresh ✅ Refreshing a specific data source using research Let's dive into the best practices for implementing these refresh methods! 🔄 Refreshing the Entire Form If you need to refresh the whole form , use the taskRefresh method. This method is useful when multiple data sources are involved, and you want to reload everything. 📌 X++ Code for Full Form Refresh public void refreshForm() {     // Get the current form instance     FormRun formRun = this.formRun();     // Check if formRun is valid before refreshing     if (formRun)     {         info("Refreshing the form...");     ...

How to Open a Form with Filtered Data Using a Button in X++ – A Step-by-Step Guide

 In Dynamics 365 for Finance and Operations (D365FO), a common requirement is to open a form dynamically from another form and pass filtered data based on a specific condition. This functionality can enhance user experience by allowing them to interact with multiple forms seamlessly, while keeping the data relevant and focused. In this blog, we’ll explore how to implement such a solution using X++, where a user clicks a button on Form 1 (such as a list of sales orders), and based on a selected record, Form 2 (such as invoice details) opens with only the relevant filtered data. Scenario Overview Let’s assume the following scenario: Form 1 : Displays a list of sales orders, and each order has an OrderID , CustomerID , and OrderAmount . Form 2 : Displays details of invoices (from the InvoiceDetails table) that are linked to the selected OrderID from Form 1 . The goal is to click a button on Form 1 , pass the OrderID to Form 2 , and display only the relevant invoice records relate...