-
Remove Country THA ,THAILAND in PND3 , PND53
Once we print out PND3 , PND 53 and Withholding Tax slip is shown as THA , Thailand , ไทย at address. We don't want this field to show in 3 reports. 1.Withholding tax (Por Ngor Dor 3) 2.Withholding tax (Por Ngor Dor 53) -
"enable in-place upgrade for usage data" and "store usage data in personalization" enabled by default.
Today in User options> Usage data> Personalization, "enable in-place upgrade for usage data" and "store usage data in personalization" are disabled by default. This product suggestion is for the users who would prefer to have it enabled by default. -
Add a numeralsToTxt method to global class for Bulgaria.
We need “Amount in words” feature for Bulgarian language and unfortunately we did not find it under the Global class. We could see few methods are there for India, FR, BR, TH and other languages. We need similar method like “numeralsToTxt” for Bulgaria as well. Pls help us to provide the method, so that we can leverage it in out code. -
Opt-in for customer raising case to pre-approve creation of support environment when raising case.
Opt-in for customer raising case to pre-approve creation of support environment when raising case. The feature already exists for Dynamics 365 CE Applications. When raising a Dynamics 365 CE Application support request, you have a check box with the following text: "I acknowledge that Microsoft may create a support environment containing a full copy of this environment to further diagnose the problem if required. This includes users, customizations, and application data."
-
When a Production suggestion is created for a "By design" issue, add the idea url to the "by design" issue.
When a Production suggestion is created for a "By design" issue, it would be great if the system could add the idea url to the "by design" issue page in LCS.
-
Original Transaction date is not correct in Ledger settlement if transaction remains unsettled across multiple YEC
If a transaction remains unsettled across multiple year-end close processes (YEC), the Original transaction date doesn't reflect the correct information after the second YEC. The expectation is that the first instance of the transaction will be used as the Original transaction date.
reference : Issue 792980 - By design
-
Change in exchange rate before adjustment causes inconsistency between Ledger and Project posting
We have identified an inconsistency between Ledger and Project posting for certain type of adjustments. Specifically, we find different results on the ledger and project side if adjustments are performed after the exchange rate relevant for the initial posting has changed.
This issue is happening in item and expense transaction. However, in expense transaction, when adjustments are made after exchange rate is changed, it only affects the posted project transaction and not the voucher transaction. In case of item transaction, it does not affect the posted project transaction, but the voucher transaction amount gets changed.
Exchange rate change can happen because of one of the reasons:
- An actual change of the default rate (because of issues or agreements).
- Because the initial posting was made with a manually set rate (it is possible to override the system rate).
- Because of the 24 hours gap between the import of daily rates.
Customer Impact: This leads to an inconsistency in posted voucher transactions and affects their financials. There is no workaround for this as of now.
Microsoft reference : https://fix.lcs.dynamics.com/Issue/Details?bugId=839678&dbType=3&qc=3e19c351be8cdf25365228d6a697702e9b006fe098b02cb40de0eaaaa41241be
-
Add a legal entity for Spain in the Contoso demo data set
Customers, Partners and Microsoft spend a lot of time troubleshooting Spanish localization issues.
Adding a legal entity for Spain in the Contoso demo data set would reduce the time spent troubleshooting.
-
For Metadata publicEnumerations, URL is showing the Label IDs only. Labels are not showing
For Metadata publicEnumerations, URL is showing the Label IDs only. Labels are not showing
-
Variance in standard cost transaction report does not tie back to postings due to landed cost
When you pull the standard cost transaction report the landed cost clearing posting is added back as a variance.
If all transactions are added together there is no PPV and the landed cost variance is the difference of the (landed cost per std cost and the landed cost on PO). However these amounts do not tie back to the variance on the std cost transaction report.