Skip to main content

Research, reread, and refresh methods on form data source in d365 finance and operations

The research, reread, and refresh methods are used to update the data displayed in a form in D365FO.

  • Research reruns the existing form query against the database, therefore updating the list with new/removed records as well as updating all existing rows.
  • Reread queries the database and re-reads the current record contents into the datasource form cache. This does not update the form controls, so you need to call refresh() after reread() to update the form controls.
  • Refresh refreshes the data displayed in the form controls with whatever is stored in the form cache for that particular datasource record.

Here is a table that summarizes the differences between these methods:

MethodDescription
ResearchReruns the existing form query against the database, updating the list with new/removed records as well as updating all existing rows.
RereadQueries the database and re-reads the current record contents into the datasource form cache. Does not update the form controls.
RefreshRefreshes the data displayed in the form controls with whatever is stored in the form cache for that particular datasource record.

Here is an example of how to use these methods:

Code snippet
// Assume that the current form has a data source named "MyDataSource".

// Update the database with some changes to the current record.
MyDataSource.update();

// Reread the current record from the database.
MyDataSource.reread();

// Refresh the form controls to show the updated record.
MyDataSource.refresh();

I hope this helps! Let me know if you have any other questions.

Labels:

Comments

Post a Comment

Popular posts from this blog

Fixing the “Can’t Stop DynamicsAxBatch” Error During Admin User Provisioning in Dynamics 365 F&O

 If you're working with Microsoft Dynamics 365 for Finance and Operations (D365 F&O) and encounter the dreaded error “Can’t stop DynamicsAxBatch” while using the Admin User Provisioning Tool , you're not alone. This guide walks you through a quick and effective solution to resolve the issue and get back to work without delays. đź› ️ What Is the Admin User Provisioning Tool? The Admin User Provisioning Tool is used to register a user as an administrator on a D365 F&O instance—typically for development and customization purposes. You provide your Azure AD credentials (email address) to gain admin access. ❌ The Problem: “Can’t Stop DynamicsAxBatch” Error While registering via the Admin Provisioning Tool or attempting to stop the service manually through Windows Services , you might encounter an error stating: “Can’t stop DynamicsAxBatch” This error prevents you from proceeding with the registration process.  The Solution: Step-by-Step Fix  Step 1: Try Stoppi...
Post a Comment
Read more

How to get batch header and recurrence information in service class for sysoperation frame work in D365 F&O

  BatchHeader batchHeader         = this.getCurrentBatchHeader();         int         timeUnitsSelected   = 0;         if(this.isExecutingInBatch())         {             RefRecId batchRecId = batchHeader.parmBatchHeaderId();             BatchJob batchJob;             select firstonly batchJob             where batchJob.RecId == batchRecId;                      SysRecurrenceData recurrenceData = batchjob.recurrenceData;             SysRecurrenceUnit timeUnits = conPeek(recurrenceData, 7);             timeUnitsSelected = timeUnits;         }
Post a Comment
Read more

Table Keys: Surrogate, Alternate, Replacement, Primary, and Foreign

Primary key A primary key is one type of key. The other type of key is an alternate key. There is a maximum of one primary key per table , whereas a table can have several alternate keys . The primary key is usually the type of key that other tables, called child tables, refer to when a foreign key field in those other tables need a relational identifier. Starting in Microsoft Dynamics AX 2012 the primary key for every new table is always enforced by an index that has exactly one field. The one field is usually an incremented number or a completely meaningless number that is generated by the system. For new tables the default is a primary key based on the RecId field. This is represented as the surrogate key in the user interface. The following table describes the  PrimaryIndex   property and other major properties that are related to keys. Property Description PrimaryIndex The drop-down list contains the surrogate key plus every index on the table that has its  Alternate...
Post a Comment
Read more