Dimension corrections tool must update all tables in the system and not just the G / L Entry
Dimension Corrections tool I think this is great in principle, because it means there is a chance that we can work without our customization in future. However, I am still lacking information at the moment to be able to assess whether the planned standard functionality can "keep up" with our own ...
To be able to delete a bank account without transactions.
Dear MS Team, Currently, a bank account without any transactions, cannot be deleted. Once any value has been entered through a means that leads to a record being created in the financial dimensions tables, it cannot be deleted. When user creates a new Bank account/vendor/customer/Fixed asset ...
Idea is noted and under review for Wave 2 2022.
Balance sheet open balances should consider account structure setup and fixed dimension value setup
In AX2012, open balance transactions were created in accordance to current account structure and fixed dimension values setup.
Unfortunately, this very useful option is for some reason no longer available in D365.
The reason, why this option is so useful is, that in cas...
I want to clarify the functionality for the year end close (YEC). The Dynamics F&O functionality for the YEC was taken exactly as it functioned in AX 2012 R3.
Account structures: In both AX 2012 R3 (and earlier) and Dynamics F&O, the account structures were never considered when bringing the balances forward into the next year. The reason for this is because the account structure could have changed, and now requires a dimension during the YEC, but the transactions posted earlier in the year don't contain those dimensions. There is no way for the YEC to default a required dimension value into those already posted transactions. Due to this, we have no intentions of changing this behavior.
Fixed dimensions: In early AX 2012 days we did apply the fixed dimension during the YEC, but support was removed early in the AX 2012 days and didn't exist on the AX 2012 R3 build used as the base for F&O. If there are clear business reasons to consider adding this back, please let us know with adding comments to this request.
Thank you!
Kristi Slininger, Finance product manager lead
Enhancement of Default financial dimensions
When you set a Default financial Dimension on a main account (legal Entity overrides) to fixed then postings automatically get corrected while posting. This however is not functioning for postings from the production module. Moreover when you set a Dimension to not fixed it is just working in ...
Possibility to reduce the amount of dimension values with another dimension
Hi,
Some customers has a need to restrict the values of financial dimension that user is able to choose on certain documents and forms.
We have for example dimensions called Level and DetailedLevel.
Dimensions are in hierarchical position so that Level ...
This functionality exists today for entry on a Ledger account form where we know the main account in use and find the account structure that shall be applied, allowing the restrictions to limit the allowed dimension values in the lookup. This is not possible on the dimensions form such as on a line of a sales order -> Line details -> Financial dimensions under the default financial dimensions group. With out the current main account to define the account structure we won't limit the values.
Longer term there is an effort to provide user (admin) defined rules around how dimension values are applied. This idea will be part of that work effort.
Opening up general ledger allocations to other posting layers
Many companies use posting layers to produce their accounting under different accounting frameworks (e.g. internal management accounts, local statutory accounting and IFRS). In order to make automatic allocations for postings to one of the layers used for corrections to a different framework, we ...
Non-deductible sales tax - ledger transaction list
In "General ledger > Inquiries and reports > Ledger reports >Ledger transaction list" it is possible to select "Sales tax specification" in the "Printout" section of the form. However, the report does not take "Non-deductible sales tax" into consideration. An example: A transaction has a sale...
Payment Reference on Advanced ledger settlement function
At the moment, the field “payment reference” is available in the form Ledger settlement only if the “Advanced ledger settlement” function is off. Once you activate the “Advanced ledger settlement” functionality, the field “Payment reference” is not available anymore. The functionality is basical...
The Payment reference has been added to the Ledger settlement page on release 10.0.32.
Option to set financial dimension values automatically for items, customers, vendors, project, etc.
Hi,
D365 ships with a lot of automatic financial dimensions such as the customer, vendor, project, etc., which are automatically crated at the time a new customer, vendor, project, etc. is created.
Quite unfortunate is the fact that those financial dimensions are automatically cr...
We are happy to announce this was delivered in October 2018. You can review the release notes here:
https://docs.microsoft.com/en-us/business-applications-release-notes/October18/dynamics365-finance-operations/data-entry-dimension-values
Sincerely,
April, GPM, Microsoft
Change the hard-coded 31 days limit to be a system parameter in of Dimension Statement report
Introduced in 10.0.29, Dimension Statement report limits the date range to 31 days for performance reason. This limit is hard-coded in the report.
I would make more sense to have this as a system parameter so that every customer can tune this range for its needs instead of li...
This date limitation has been removed, allowing customers to generate the report for more than 31 days.
Administrator
Just to be clear the data maintenance tool now shipping in the product and includes actions for correcting and reconstructing dimension data is largely fixing the data in the Dimension* tables that hold references from any sources that are dimensions. All transactions such as GL transactions and CustTrans or similar should hold a reference to the dimension data (RecID) from .LedgerDimension or .DefaultDimension fields.