Microsoft announced the deprecation of Visual Studio 2022 for X++ development.
Starting with Platform Update 74 (10.0.49), Visual Studio 2022 is no longer supported for X++ development. The only supported IDE is Visual Studio 2026.
The general availability of Platform Update 74 (10.0.49) will be in September 2026, so there is plenty of time to prepare a migration plan and get ready for the new update.
Microsoft is hereby announcing the deprecation of the Regression Suite Automation Tool (RSAT), effective May 15, 2027.
As of that date, Microsoft will no longer provide support, maintenance, bug fixes, or feature enhancements for RSAT. Customers may continue to use RSAT after the effective date; however, the product will remain available only on an unsupported basis.
This decision reflects Microsoft’s continued investment in modern testing approaches that support broader automation scenarios, greater extensibility, and long-term platform evolution. RSAT was developed primarily for Finance and Operations scenarios and does not address the broader end-to-end testing requirements that many organizations now have across connected applications and business processes.
Customers should evaluate alternative testing solutions in accordance with their business and technical requirements, including offerings from the broader ecosystem of third-party testing vendors.
I recently faced errors in the Unified Developer Experience (UDE) environment while trying to deploy a model. However, there were no build errors and my model had no dependencies on other models.
In order to find the root cause of the issue, we should see the log file.
In order to add yourself to the System Administrator role in the PPAC environment, you need to perform the following steps:
If you are going to upgrade your developer cloud-hosted (OneBox) environments to version 10.0.46, you may face an issue at step 28. The issue is related to Visual Studio 2022.
If you are currently using version 17.10 or earlier, please update to version 17.11.5 or later. Once you have updated, try/retry the update process again.
Once, I experienced a database synchronization issue: "Table Sync Failed for Table: XXXXX. Exception: System.InvalidOperationException: Database execution failed: Column name 'XXXXXX' does not exist in the target table or view."
I had checked the table structure in my local DevBox and the mentioned field was present in the table. I checked the table structure on my local DevBox, and the mentioned field was present. When I checked the field's properties, I recognized that it has the "SaveContent" property set to "No" and is included in one of the table's indexes.
I set the "SaveContent" property set to "Yes" and performed a compilation and database synchronization. After that, the error "Table Sync Failed for Table: XXXXX. Exception: System.InvalidOperationException: Database execution failed: Column name 'XXXXXX' does not exist in the target table or view." disappeared.
When a set-based operation is used (e.g., update_recordset or insert_recordset), and an error occurs with the message "Cannot insert the value NULL into column 'Name', table 'TableName'; the column does not allow NULLs. UPDATE/INSERT fails", it means that no corresponding record was found in the joined table, so a null value was fetched and tried to be inserted into the table's column.
It can happen if values are obtained from outer-joined data sources when there is no corresponding record in the outer-joined table, and thus a null value is retrieved.
Another case is when values are obtained from views, and those views contain calculated columns whose values can be "empty".
The solution can be using "inner join" with update_recordset and insert_recordset commands, or by using a standard "while select" clause with a view that has calculated columns.
For example, if the view is used and the code below throws the mentioned error: "Cannot insert the value NULL into column 'Name', table 'TableName'; the column does not allow NULLs. UPDATE fails"
TableForecast tableForecast;
update_recordset tableForecast
It is an example of how it can be changed to avoid the error.
while select forupdate tableForecast
In some cases, we need to modify the values of system fields. Below is a code example of how to do this. The key points are the "OverwriteSystemFieldsPermission" and "overwriteSystemFields" commands:
public void insert()
this.overwriteSystemfields(true);
public void update()
public void setAuditFieldsAnonymous()
if (createdByField.isSQL())
Based on announcements regarding Microsoft Dynamics 365 Finance & Operations, February 16, 2026, marks a major shift in how environments are managed, with the transition of key capabilities from Lifecycle Services (LCS) to the Power Platform Admin Center (PPAC).
Creating all new D365 Finance and Operations (F&O) cloud implementation projects will be routed through the Power Platform Admin Center (PPAC), rather than created in the LCS, which has been the traditional approach for years. As a result, environment actions, support motions, and governance checks will be moved to be in PPAC, not assumed from LCS.
Environment actions, support motions, and governance checks will be moved to be in PPAC, not assumed from LCS.
Existing projects, on-premises deployments, Commerce, and AX 2012 upgrades will continue to use LCS for the time being. To migrate existing LCS projects to PPAC, Microsoft provides a guide.
We have a class that is implemented using the SysOperation Framework and needs to be added to the "Batch task" form (System Administration > Batch > View Task) so that we can define execution parameters. For example, we need to set dependencies, sub-tasks or the execution sequence between batch jobs. In this case, we need to use the "SysOperationJournaledParameters" attribute.
I found an example in the "Automatic release to warehouse" operation and adjusted it to my needs. I made the following modifications:
1. Added the "SysOperationJournaledParameters" attribute to the controller class:
2. Added the service class and its methods to the "construct" method:
The fastest way to restart AOS Service in Unified Developer Experience (UDE) environment is to Start/Stop FO Online Debugger in Visual Studio.
I figured it out based on my experience, but later, I found some useful tips here: https://learn.microsoft.com/en-us/power-platform/developer/unified-experience/finance-operations-faq#stopping-debugging-restarts-the-runtime
In some cases, the Dynamics 365 Finance and Operations Unified Developer Experience (UDE) environment may not be available, and returns:
Based on my experience, there are several options to fix this error:
The data contract is a class that is the parameter for the entry point to the class that performs the process. The SysOperation framework automatically creates a dialog from the data contract, which will use the EDTs in the contract to provide the label, and even drop-down lists based on the table reference on the EDT.
or with the SysOperationContractProcessing
When you add the parm methods to the contract class the field will be added to the user dialog.
From a technical perspective, data-contracts can implement different interface classes.
The main goal of this interface is to implement the contract initialization. If you want to initialize the default parameters in run time before the UI interface is displayed to the user, you need to implement the SysOperationInitializable class.
class EAMWorkOrderAddNoteDescriptionContract implements SysOperationInitializable
In this case method "initialize" will be available and can be rewritten. This method is used to initialize variables within the data contract. However, this method is called if no user usage data is found.
In case the method "initialize" must be called at any time you have to add the SysOperationAlwaysInitializeAttribute to your contract.
In addition, if you want to clean up the field value on the dialog, it is required to add the same SysOperationAlwaysInitializeAttribute attribute to the desired method:
The main goal of the SysOperationValidatable interface is to implement the contract validation. It allows you to validate the values provided for the data contract. For example, when users enter the field value on the dialog and press the “OK” button the "validate" method of the data contract will be called.
From a code perspective, its implementation looks like:
class CustRecurrenceInvoiceDataContract implements SysOperationValidatable
In addition, you heed to override the "validate" method:
The SysPackable interface implementation forces the data contract class to create the "pack" and "unpack" methods which means that we can do serialization on it, like pack and unpack the variables defined in the #CurrentList for the #CurrentVersion macro.
If you are going to upgrade your developer cloud-hosted (OneBox) environments to version 10.0.44, you may face an issue at step 27. The issue is related to Visual Studio 2022.
A new version of Visual Studio 2022 has been released to address this issue. If you are currently using version 17.14.2 or earlier, please update to version 17.7 or later. Once you have updated, try/retry the update process again.
As you probably know, approximately in one year after the release of version 10.0.41, support for inventory transactions support for internal warehouse operations will be removed and all customers will be required to move to warehouse-specific inventory transactions for tracking on-hand inventory for internal warehouse operations.
It seems that Microsoft will release a fix for a cache performance in version 10.0.44. (https://fix.lcs.dynamics.com/Issue/Details/?bugId=976894&dbType=3)
Based on the description of the fix, currently, any insert operation is flushing everything from the found cache, across all AOSes. When a record is inserted into another AOS, then the cache is flushed. In fact, it means that each AOS has to recache the data.
As far as I know, today any update/insert/delete triggers an update in SysCacheFlush, forcing other AOSes to flush whatever data they have cached.
I guess, the fix is to stop flushing for inserts on Found cached tables. Therefore, an insert into a table where found data is cached will not require any cache invalidation (flushing).
In some cases you may face an issue with a model or project build in a Tier-1 environment.The error can be "another x++ build is currently running" or "another build is in progress".
I guess, advice on how to solve this problem can be easily found on the Internet. For example, you can restart your virtual machine or kill the build process (xppcAgent) manually and try again.
I believe it would be great to know the reason for this issue. In Visual Studio 2022, there is a setting called "Build Modules in Parallel". If it is enabled, you might constantly face the issue mentioned above.
As you might know there are a lot of controls and related macro commands in the WHS classes. It is not really convenient to search for macro commands in code, since they are not supported by the cross-reference feature.
In D365 Finance and Operations, there is an option that can help simplify the development of warehouse mobile flows and tracking using the existing commands. It is constants.
In my opinion, the best example of the mentioned option is the "ProcessGuideDataTypeNames" class. Inside the class you can find a lot of constants that are used in the mobile device flows.
As you can see, macros are used at the class declaration level, but with a specific reference to a value in the WHSRF macro. As a result, you can use cross-references to find all the places in the code where the constants are used.
When I ran data upgrade using Data Upgrade 10.0.41 package, I faced an issue:
On the Internet, I found that there might be a problem with a version of the SQL Server PowerShell module. When I installed the latest 22.x.x version I was able to resume the process. I performed the following steps:
