Yuji Imaoka

We are considering sharing information on SRs submitted by other projects within the company.

However, Issues and solutions are not output in Manage incidents page of LCS.

We would like to request to add one of the following functions.

(1) A function of LCS to search SR issues and solutions submitted by members of the same company, like Issue Search.

(2) Display Issues and solutions for each SR in Manage incidents page of LCS.

(3) LCS API for programmatic retrieval of Issues and solutions corresponding to SR numbers.

(Problem)

Reversing a general journal with a project reference isn't possible.

[Manual entry of reversing journal entries] takes time to implement and prevents timely month-end closing. This is not an effective workaround, and the business impact of this issue is significant.

Previously, when another customer pointed out the same problem (Issue 414025), Microsoft stated that the impact on other customers would be monitored. However, despite another customer highlighting the significant business impact, this issue was not fixed.

Please set a deadline to fix this issue as it affects many customers.

Issue 987726 Reverse entire journal is not possible when the journal contains journal entries of account type Project.

Issue 414025 Not able to reverse vendor invoice journal when offset account is selected as project

We request that D365fO's standard functionality includes mechanisms to handle transient database disconnections.​

Specifically, we would like the platform to implement automatic reconnection processes at the platform level when such disconnections occur.​

Details

Microsoft advises implementing custom exception handling to catch the TransientSqlConnectionError exception in add-on programs.

However, since this handling is not provided in the standard features, such disconnections result in abnormal terminations of both online and batch processes.​

As a result, we are experiencing frequent "temporary issues" due to transient database disconnections.​

AX2012 had settings in the Server Configuration to handle such scenarios at the kernel level:​

• Number of connection retries
• Connection retry interval​

These settings allowed the system to automatically attempt reconnections to the database upon disconnection.​

Therefore, we request that D365fO also implements automatic reconnection mechanisms at the platform level to handle transient database disconnections effectively.

Since March 2025, there have been many cases of package application failing in D365fO.

Although individual issues have been resolved, Microsoft engineer have said that they cannot guarantee that package application will be 100% successful, and that partner or customer must monitor package application.

Since package application is performed late at night or on weekends, there are the following problems.

(1) Additional costs are incurred.

(2) The engineer will have to work outside of working hours.

We request that Microsoft implement a feature that eliminates the need for engineers to monitor package application.

For example, automatic retry until a specified time.

Issue Description:

When creating a new Consolidated invoice for Japan, the runtime parameter for currency is fixed to JPY. As a result, consolidated invoices cannot be created for customers with foreign currency transactions (e.g., USD).

This issue occurs when the Japan Invoice support feature is enabled.

Request:

Please make the following improvements:

a. Enable the creation of Consolidated invoices for Japan regardless of the transaction currency.

b. Ensure that when a consumption tax discrepancy occurs, the adjustment entry (consumption tax transaction) is correctly created even for foreign currencies.

Issue Description:

When using the Post button on the Consolidated invoices for Japan page, a general journal entry is created and posted. However, the journal name used in this process cannot have approval and workflows configured. If such settings are applied, an error occurs when clicking Post button on the consolidated invoice page.

As a result, it is not possible to prevent a malicious user from using the journal name on the general journal page to post journal entries without any approval.

Request:

Please fix this so that malicious users cannot post journal entries using the posting function on Consolidated Invoices for Japan page without anyone's approval.