Dynamics 365 Blog - Posts from January 2020
Exception during Platform update 30When I recently wanted to update a local D365-VPC with Platform Update 30, the following error occurred at Step 19:
The reason for this error was quickly found - after downloading the VHD from LCS, the name of the virtual computer was changed, but not all neccessary steps were done. As a result, SQL Reporting Services had a problem, a new database had to be entered here. How this works, and what else you have to consider when renaming a VHD, can be found here. |
Error "The step failed" during platform update 30 in connection with reporting servicesIf the following error occurs during a platform update of a local VPC...
...may be the reason that the computer name of the VHD has been changed, but not all steps recommended by Microsoft have been performed. What they are can be found here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming
|
Display financial dimension as display method[SysClientCacheDataMethodAttribute(true)] public display DimensionDisplayValue displayLedgerDimensionValue() { return LedgerDimensionFacade::getDisplayValueForLedgerDimension(this.LedgerDimension); } |
|
|
|
|
|
|
|
In principle, every solution in Dynamics 365 for Finance and Operations should be free of best-practice deviations, but sometimes there is the need to suppress them.
Such a case are for example, event handlers that have a predefined parameter profile, but if one of these parameters is not used, it causes a BP deviation.
With the above EH, the following BP deviation would be output because the parameter e is not used: