Dynamics 365 Finance

Ticket number TrackingID#2505050040012911

The SubBillDeferralTransactionLineDeferralEntity only accepts Sales Order and General Ledger entries. There are several customers using Deferrals for Item Requirements, AP, and POP. 1) There is currently no method available for these customers to import Open records for data migration off a legacy system. 2) There is also no way for customers migrating from Revenue Recognition using item requirements over to sub bill deferrals.

Please add these 2 MSFT offered solutions to the standard release. Otherwise ALL customers wanting the functionality will have to build extensions for every implementation

In the class SubBillDeferralTransactionLineDeferralEntity, there is a method called mapDeferralEntity inside which you can handle the cases for SubBillTransactionType::SalesOrder or LedgerJournalTrans.

You can add a piece of code like shown below, to address the gap in entity for Sales Orders of sales type ItemRequirement.

An extension can be written for this method to add this logic.

Now, with another approach, in the same entity class SubBillDeferralTransactionLineDeferralEntity and in the same method, where we are manually setting the values in insert_buffer (SUBBILLDEFERRALTRANSACTIONLINEDEFERRAL). In this section, the system is setting values imported from the file.

Allow us to select whether financial dimensions for Employee Expenses default from the Employee record, or the employee-linked Vendor record

Currently the financial dimensions always default from the Employee record

Dear Microsoft Team

In process automation,we do auto settlement of main accounts, where it settels main accounts by matching amounts only. My suggesions are as below

1. It should also match business unit (cost center) dimension, document number etc.
2. It asks Start and End Date, But eventhough it settles records that have transaction date below start date

Regards,

DEEPAK PANCHAL

The current file filter is limited.

For example i have a client who would like to exclude all files with "clockify" in the file name. The exclude option only alllows a specific filename to be used, rather than a specific phrase in a file name.

For example *clockify*.

This would save money on the subscription count.

 The Reporting Currency feature for one of our existing legal entities in Dynamics 365 Finance and Operations.

Our implementation partner has advised us that activating this feature requires closing the current legal entity and creating a new one with the Reporting Currency option enabled

In the current design of the electronic document submission log for batch submission scenarios, users must navigate into each batch to view key details. To improve usability and efficiency, we propose adding two new columns to the submission log view:

• Total Invoice Amount: Displays the aggregated value of all invoices submitted in the batch.
• Store/Warehouse Origin: Identifies the originating store or warehouse for each batch.

Given that each batch typically corresponds to a specific store or warehouse in retail operations, this enhancement would provide immediate visibility into critical data without requiring additional clicks. It would significantly reduce the time spent on manual lookups and streamline the monitoring process.

This improvement would enhance the overall efficiency of the product and deliver measurable time savings for end users.

We encountered an issue along Demand forecast lines that when data is being uploaded for 1 budget model (eg: RE 100) and after saving it if we are uploading other data for another budget model (eg: RE 200) then the data in 1st budget model (RE 100) is getting completely replaced and if we check the 1st budget model (RE 100) then it becomes blank with no data at all. However, the new uploaded data appears in new budget model (RE 200).

After reviewing the backend, it was found that the data entity being used for this process is ForecastDemandForecastEntryEntity, through which the data is imported into D365 F&O.

The primary key, or unique identifier, for this data entity is ForecastEntryNumber. Therefore, if the line number in the Excel file is not changed, the system will not delete the forecast lines but will instead update the existing data. This is because the system recognizes that the line number corresponds to an existing entry and will treat it as an update, not a deletion.

Upon reviewing, it was observed that the RecId remains unchanged when the data is imported after modification under a different model. As this behavior is aligned with the current design of the standard data entity, the system works as expected. In the current design, if the user modifies an existing line without changing the line number, the system assumes that the user is updating the existing data.

For adding new data, the user should enter a new line number for the new data as per the current design.

There is this report called PRODUCT RECEIP JOURNAL under Accounts Payable - Enquires and Report. It shows the product receipt posted during given period.

If we can add extra column which shows whether a particular Product Receipt is booked or not. This will be very userful.

When an initial e-invoice submission fails, the status in the Electronic Document Submission Log remains “Failed”. Even after a successful related submission, the original log entry does not update. Users must manually navigate to Inquiries > Related submissions to find the latest status. This makes Submission status unreliable and time-consuming to use for tracking submission outcomes.

We would like to propose a design change request that involves either:

• A status override or chaining mechanism in the submission log to reflect the latest related submission.
• A visual indicator or link in the original failed submission pointing to successful related submissions.
• A consolidated view that merges submission history for the same document.

Terms of payment is not available in invoice capture for PO invoice