Technical (D365FO)

Msedge Igbjxe2zsz
Dynamics 365 for Finance and Operations, Technical (D365FO)

The database could not be exclusively locked to perform the operation

The previous script for renaming a database in a Tier-1 cloud environment resulted in an error due to exclusive locking issues. The recommended solution involves setting the database to single-user mode, renaming it, and then reverting to multi-user mode before renaming the new database to the desired name.

blog 02
Dynamics 365 for Finance and Operations, Technical (D365FO)

D365: When and how to use mapEntityToDatasource() method

This method, mapEntityToDataSource(), is used in Dynamics 365 for Finance and Operations to initialize datasource fields or create datasource table records while importing data. It checks for existing records and initializes fields based on specific conditions. Understanding data entities and management is essential for utilizing this method effectively.

blog 02
Dynamics 365 for Finance and Operations, Technical (D365FO)

D365: Get worker email address by purpose in X++

This content demonstrates how to obtain a worker’s email address based on a specific purpose, such as “Purchase Order,” within Dynamics 365 for Finance and Operations. It includes a solution involving an extension class of the HcmWorker table to achieve this, using a provided code example for reference. The method can be called to initialize a temporary table buffer.

blog 02
Dynamics 365 for Finance and Operations, Technical (D365FO)

D365: Add field to New released product dialog form and persist to table

This post demonstrates how to persist a custom field added to the New released product dialog form to the table in X++ in Dynamics 365 for Finance and Operations. The solution extends the EcoResProductCreate form and uses chain-of-command to add the new fields to the data2Controls container. The code provided illustrates this extension.

blog 02
Dynamics 365 for Finance and Operations, Technical (D365FO)

D365: How to make a standard field mandatory on a form in X++

This post explains how to make a standard field mandatory on a form in X++ within Dynamics 365 for Finance and Operations. The business requirement is to enforce a field that is optional in Standard Dynamics. The solution involves extending the PurchCreateOrder form using chain-of-command to make the Buyer group field mandatory on the form datasource.

Scroll to Top