Dynamics 365 Finance

Currently, when a lease is linked to a fixed asset, terminating the lease automatically closes the associated fixed asset.

There should be option that allows the fixed asset to remain active after the lease termination. This would enable continued use of the asset even when the lease contract ends.

This functionality is essential for scenarios where the lease agreement concludes, but the fixed asset remains available for ongoing operations.

Currently, when the field ‘Confirmations, delivery and invoicing on hold’ = ‘Tax Invoice’ is set on the Customer Master, sales order invoices are blocked from processing, while other transaction types such as Customer Free Text Invoices and Customer Payment Journals are allowed to process under certain conditions.

For example:

• A credit Free Text Invoice processes successfully, but a debit Free Text Invoice fails.
• A credit Customer Payment Journal processes successfully, but a debit Payment Journal fails.

This behavior makes sense as it prevents increasing the customer’s balance while allowing reductions.

However, credit Sales Order Invoices, which also reduce the customer’s balance, are currently blocked from processing. 

Suggestion: Sales Order Invoices—especially credit transactions—should be allowed to process when they reduce the customer’s balance, just like the other transaction types. This would ensure consistency across invoice and payment processing logic and reduce manual workarounds.

At present, the system supports configuring alerts at the individual batch job level, enabling notifications for job completion, failure, or cancellation. However, it lacks native functionality to set alerts at the batch group level. As a result, when dealing with batch groups containing hundreds of jobs, each job must be configured separately to enable alerts making the process time-consuming and inefficient. We're therefore exploring a solution that enables more streamlined monitoring and faster issue resolution.

Issue Context: In Dynamics 365 Finance and Operations (D365FO), when importing general journal lines using “Data Management” or “Excel Add-Ins,” it has been identified that the UUID field (CFDIUUID_MX) —required by Microsoft’s Mexican localization— is not available in the standard data entity General Journal Account Entry. Although this field exists in the journal lines interface, it is not exposed for mass import/export operations.

Operational Impact:

• Affects multiple Mexican companies.
• The absence of the field prevents compliance with Mexican fiscal requirements.

Key Findings:

• The UUID field appears in the journal lines screen for Mexican users but is not available in the data entity for import.
• The “Insert Columns” feature allows manual addition of the field, but this is not viable for bulk operations.
• It has been confirmed that the CFDIUUID_MX field is missing from both the import template and the field mapping in the entity.

Expected Outcome:

• Modify the General Journal Account Entry entity to include the UUID field (CFDIUUID_MX).
• Ensure it is available for both data import and export actions.
• Make the field visible in the Excel Add-In template by default.

The report "Service Declarations F01DGS" is currently unavailable in D365 Finance and Operations. However, it is essential for compliance with Belgian legal requirements. While this report is already available in Business Central, our customers have expressed a strong need for the report in D365 Finance and Operations to ensure seamless operations and adhere to local regulations.

When employee opens "Unattached expenses" function from "Employee self service" and adds some expense lines to her/his expense report than default dimension inheritance is not being executed.

Adding or removing Project ID to expense line does not have any impact on financial dimension values on this expense line (despite of correct rules/conditions being present in "default dimension inheritance" functionality).

As the result, expense lines processed with the use on "Employee self service" workspace have inaccurate financial dimension values in accounting distribution.

This problem does not occur if expense lines are processed in Expense Management module.

I suggest that execution rules for "default dimension inheritance" should be reviewed for Employee self service/Unattached expenses, so system inherits/recalculates financial dimension values whenever any change is made to Project ID on expense line. This would bring that functionality in line with how it works in Expense Management module and improve posting accuracy.

Described issue was experienced and persists in D365 Finance & Operation version 10.0.41 (10.0.2015.78).

Financial tags cannot be used in reports in BPA. It is really missing when a company uses it for financial reporting.

Financial dimensions are not enough for some analytics reporting.

When pushing a personalized/published view or workspace to (multiple) users, it is not clear if the view/workspace has been succesfully pushed to all users. In the past we have noticed that sometimes views are not pushed correctly to all the users, but only to some users. A validation would be more sufficient to follow up on this.

The parameter named "Maximum Batch Threads" on the "SysServerConfig" auto defaults to 16 ever night even if you change it. This is due to batch auto scaling (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-capacity#batch-auto-scaling). Considering it can't be effectively changed by users. This should be either removed or disabled.