Dynamics 365 Finance

Now D365 for sales order and purchase order take the delivery header date to calculate the cash flow forecast.

The suggestion is to use the delivery date (requested or confirmed if we have the confirmed delivery date) in sales and purhcase order line in order to have the correct projection of cash flow.

There is a tax requirement in Italy to pay stamp duty calculated on the number of transactions in the fiscal journal. The article from the Italian Finance Ministry: Tariffa Articolo 16. We are unable to calculate the number of documents in the file because in the current version of the fiscal journal which lists all the vouchers and journal entries in order of posting date, system assigning one line number to each line of a voucher when expectation is to assign one line number to the transactions of the same voucher.

Using Excel to calculate the number of documents is very tedious and after certain lines it is impossible to manipulate the file, which is too heavy with merged cells.

The existing display shows line numbers as shown below :

Line no.  Posting date Competence date Docum. no.    Date for document. Ledger account Account name

00000001 20/06/2024    20/06/2024    GA0177232 31/01/2024    607010    Acquisti di merci in Italia - Dropship

00000002 20/06/2024    20/06/2024    GA0177232 31/01/2024    401100    Fornitori di merce Nazionali

00000003 20/06/2024    20/06/2024    GA0177232 31/01/2024    445660    I.V.A. su altri acquisti di beni i

00000004 20/06/2024    20/06/2024    GA0177232 31/01/2024    624300    Spese di trasporto su vendita -

00000005 20/06/2024    20/06/2024    GA0177233 31/01/2024    607010    Acquisti di merci in Italia - Dropship

00000006 20/06/2024    20/06/2024    GA0177233 31/01/2024    401100    Fornitori di merce Nazionali

00000007 20/06/2024    20/06/2024    GA0177233 31/01/2024    445660    I.V.A. su altri acquisti di beni e

00000008 20/06/2024    20/06/2024    GA0177233 31/01/2024    624300    Spese di trasporto su vendita -

The result should be as follows. It should be noted that at the end of 2023 we migrated to D365-FO from a very old IBM AS400 tool, which displayed data as shown below. This avoids tedious and useless manipulation of a fiscal document. 

Line no.  Posting date Competence date Docum. no.    Date for document. Ledger account Account name

00000001 20/06/2024    20/06/2024    GA0177232 31/01/2024    607010    Acquisti di merci in Italia - Dropship

00000001 20/06/2024    20/06/2024    GA0177232 31/01/2024    401100    Fornitori di merce Nazionali

00000001 20/06/2024    20/06/2024    GA0177232 31/01/2024    445660    I.V.A. su altri acquisti di beni i

00000001 20/06/2024    20/06/2024    GA0177232 31/01/2024    624300    Spese di trasporto su vendita -

00000002 20/06/2024    20/06/2024    GA0177233 31/01/2024    607010    Acquisti di merci in Italia - Dropship

00000002 20/06/2024    20/06/2024    GA0177233 31/01/2024    401100    Fornitori di merce Nazionali

00000002 20/06/2024    20/06/2024    GA0177233 31/01/2024    445660    I.V.A. su altri acquisti di beni e

00000002 20/06/2024    20/06/2024    GA0177233 31/01/2024    624300    Spese di trasporto su vendita -

Looking forward to your feedback.

Advanced bank reconciliation: transferring the bank statement number into Document number (LedgerJournalTrans.DocumentNum) of the automatically generated and posted journal line (e.g. if you process reconciliation matching rule "Settle customer invoice", generating a customer payment journal) would improve visability on customer/vendor/ledger transaction. Actually, only the voucher number is visible and the users cannot directly see, e.g. which bank statement was used to post a customer payment transaction!

Add controls to enable users to prevent posting to the sales tax ledger based on financial period and legal entity, similar to the existing controls found in the Ledger calendar form.

This control should take into account whether the company is configured to use the Date of VAT register functionality or not.

Let the system reset an initiated production batch order to released when the manufactured item works with CW and reported as finished qty is higher than the estimated.

Detail example case:

Manufactured item with CW, serial & batch number tracking dimensions

Estimated qty: 4 CW units * 3,78 (nominal inventory qty defined on the item) = 15,12

Reported qty: 4 CW units * 5,43 inventory qty = 21,72

The system is not able to reset status to released done that is not able to post the reported as finished journal and returns error message 'Split quantity must have the same sign as the transaction.'

Issue has been reported to MSFT and resolved as 'feature limitation'

To control the export or download access for the reports, there should a security role which can be given to the desired users.

We need to automate bacpac upload from local machine to LCS Asset Library via PowerShell or Pipeline DevOps. currently there is no APIs to upload bacpac via Pipeline DevOps, so we need to have this feature available very soon.

It would be good to groups payment fees from vendor/customer payments within the new "Ability to post detailed vendor and customer payments, but summarize amounts to bank account" feature, as it happens in real life scenarios.

According to our documentation:

If you navigate to a page and that entry point includes a query, the original query will execute originally in place of the default view's query. You should be alerted when this occurs via an informational message when the view is loading. You can also confirm by switching to this view after the page loads, as that should allow the view query to execute regardless.

There are several cases of customers raising this issue.

Is there's anything that could be done in order for the default queries to run when navigating to a page instead of running the page's original query?

Thank you in advance for your help.

"Whenever using the formular “Assign users to roles” in System administration the button “Manually assign / exclude users” cannot be used when a role merely has the user "Retail Service Account" is applied.

This is in my eyes completely randomly assigned to of roles.

This, unfortunately, inhibits the system admin to assign roles to a huge number of users.

However, this upcoming cannot be seen, once another user is assigned to this role: 

As there is a Microsoft document that inhibits us to delete the Retail Service Account" this functionality cannot be used although it is tremendously important to our customers.

The functionality of a(s)signing Users to a role is the most convenient way to assign roles to users.

This functionality is inhibited by the "Retail Service Account" which is not allowed to be deleted due to the MS rules.

Please, review this Bug and enable the Button "Manually assign / exclude users" in the "Assign users to roles" table to make the product more convenient for usage."