Alternate for Accounting source explorer
Hi Please have an alternative for Accounting Source Explorer in D365 Finance and Operations. It has always had a bug every time we upgraded D365. For example, today, when I tried to run "Accounting Source Explorer" in D365 for cash account.
We paid an EFT to 20 vendors. Instead of showi...
Need to improve the efficiency to add more Financial dimension in account structure.
In Dynamics we have a provision to create good number of financial dimensions however we can add only 7 to 11. We have multiple customer according to their business needs they should use more the 16 Financial dimensions. I totally believe right now we have some limitation to add more then 10 fi...
Add “Last Closed Fiscal Year” field to Year End Close screen
Add “Last Closed Fiscal Year” field on the General Ledger > Period Close> Year End Close screen so users can see the last fiscal year that has been closed on this screen. This would be a nice way to double-check that fiscal year ends have been run without having the check if the RE earnings entr...
A full audit trail of the year-end close has been added with the feature "General ledger year-end enhancements". This is automatically enabled as a feature on build 10.0.25.
Add Reverse Button to Journals form and Accounting Source Explorer form
Add the Reverse button to the Accounting Source Explorer form and the General Journals form. Users don't often look for posted journals on the main account transactions form unless they have to. That isn't where they instinctively go. They go to the general journals forms and the Accounting So...
The Mass reversal feature added the ability to reverse transactions through the Journals, but only if the transactions were 'reversable' to begin with. Not every transaction can be reversed, and those limitations are still in place. The ability to reverse from the Accounting source explorer will be considered under another Idea, which will look at general improvements to the inquiry.
General ledger description length increase from 60 char to 512 char
The request is to increase the length of the description from 60 characters to 512 characters to fit customers requirements, some transactions contain larger descriptions and this is lost with the 60 characters limitation.
The size of the description has been increased to 512 characters.
Administrator
Thank you for this idea. A future version of the product will look at this with a larger re-write. Modifying the existing code to allow more is very costly exercise with great risk to existing customers.