Comments
This is definitely not an enhancement but a major bug that needs fixing ASAP. I can run Close Income statement on a sandbox that has already been run on V27 - so there should be no journal entries but there are hundreds,Tried running on Production database that only really needed a couple of journals after minor adjustments after previous income Statement close with V27 and it hangs because so many journals are created.The Income Statement batch job is fundamental to year end closing.I suggest Microsoft revert to the version that was working for everyone in 28.2 and then whatever adjustment they were trying to do around additional currencies they redo and thoroughly test before they put it back out again.
Any news as to when this will be handled? Our groups often have SOs with partial shipments/invoices where the last couple Items on backorder are eventually removed from the SO as they would take too long to fulfill. When this occurs the Sales team loses visibility to the document attachments they added from the initial partial shipment/invoices.
This is an important feature. I tested the preview feature of uploading an existing template to transform from pdf to Inspection in Dynamics. Almost all questions were added as textbox single-line, but I needed numbers for some and checkboxes for some. This meant I had to insert questions again as it is not possible to change type on an existing question. MS has this feature in Forms, so should easily be amended to this product as well.
The inspections need to take a better advantage of data already in the system. You should be able to edit layout of the pdf (logos etc.) and insert inspector, date etc. Also need the ability exclude some questions/pages, as some may be for internal use only and not of interest to the customer.
We consider this a critical accounting issue. For customers using foreign currencies, the behavior introduced in 28.3 can negatively impact transparency, auditability, and confidence in the closing process. Financial year-end closing is one of the most sensitive accounting operations, and creating thousands of apparently identical entries makes validation and reconciliation unnecessarily complex. In our opinion, this increases the risk of accounting errors and can leave customers with the perception that the general ledger is no longer in a stable and trustworthy state. Microsoft should treat this as a high-priority issue and restore the previous behavior from version 28.2.