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...");

        formRun.task(#taskRefresh); // This triggers a full UI refresh

    }

    else

    {

        warning("FormRun is NULL. Refresh skipped.");

    }

}

🔍 How It Works

1. Gets the form instance using this.formRun().
2. Checks if formRun is not null (to avoid errors).
3. Calls formRun.task(#taskRefresh) to refresh the entire UI.
4. Displays an info message when the refresh happens.

💡 When to Use?

• After inserting or updating records that affect multiple data sources.
• When you want to ensure all changes are reflected in the UI.

---

🔄 Refreshing a Specific Data Source

Instead of refreshing the entire form, sometimes you just need to refresh a specific data source. This can improve performance by reloading only the required data.

📌 X++ Code for Data Source Refresh

public void refreshDataSource()

{

   Table_ds.research(); // Refreshes only this data source

}

🔍 How It Works

1. Calls research() on the specific data source to reload data.
2. Does not affect other data sources in the form.

💡 When to Use?

• When only a single table is updated, and you don’t need to refresh the full form.
• To improve performance by avoiding unnecessary UI reloads.

🔄 Bonus: Ensuring Data Accuracy with reread()

If you're updating records but haven’t committed the changes to the database yet, you should use reread() before research().

public void refreshDataSource()

{

    Table_ds.reread(); // Reloads the latest uncommitted data

    Table_ds.research(); // Refreshes the UI

}

📝 Conclusion

Refreshing forms in D365FO is crucial for ensuring a smooth user experience. Depending on your needs, you can:
✅ Use taskRefresh to reload the entire form.
✅ Use research to refresh a single data source.
✅ Combine reread() + research() to handle unsaved changes.

By implementing these best practices, you’ll improve form responsiveness and data accuracy in your D365FO applications! 🚀