Upgrade notes affecting specific modules

-
Asset depreciation schedules (ITA)
Issue: Field mapping issue may cause inaccurate depreciation schedules
Modules affected

GDL, General ledger, Fixed assets

Versions affected

Microsoft Dynamics AX 3.0 and 4.0

Upgrade note

A field-mapping issue has been identified that could cause a company to lose data in the AssetDepreciationProfile table during the upgrade to Microsoft Dynamics AX 2009, leading in some cases to invalid proposed depreciation schedules. This risk of data loss is possible only when the following conditions are met:

The Italian configuration key is enabled for a company

Depreciation profile records have been created for that company with these settings:

The method is set to Manual

The interval is set to Yearly

The calculation base is set to Months

Because of this field-mapping issue, the CalculationBase field in the AssetDepreciationProfile table will be dropped when the upgrade to Microsoft Dynamics AX 2009 is performed. (In a depreciation profile, the value of base enum CalculationBase determines whether to calculate a depreciation interval on a daily or monthly basis.) If the field is dropped during upgrade, it will be recreated with a value of 0, which represents the interval Days. This change would then yield incorrect results when depreciation proposals are generated using this particular depreciation profile, which previously had been set to Months.

To resolve this issue after the upgrade process has completed, you can review and reset the calculation base values to Months in the Depreciation profiles form (General ledger > Setup > Fixed assets > Depreciation profiles).

Source

Comments

Post a Comment

Popular posts from this blog

How to disable auto enabled flight key using KillSwitch

-
Image
Microsoft is introducing new functionality into Dynamics 365 for Finance and Operations with flight keys in every other new release. For this they use  Flight  classes so that the changes are automatically applied and can be reversed.  Example of a flight class that control the functionality of a new set of functionality.  When a flight key that enable functionality can be found in the flight key table  SysFlighting To disable the functionality don't delete or change the enabled flag on the flight record, instead insert a KillSwitch  record. The KillSwitch record will ensure that the flighed functionality will stay disabled as long as it exist in the flight table.  In an environment that Microsoft maintain can raise a support ticket in LCS to disable specific flight keys.  SQL statement for insert the KillSwitch record.  DECLARE @flightName NVARCHAR(100) = 'WHSWorkCancelForcedFlight_KillSwitch' IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName
Read more

Technical intro to Feature management in D365FO

-
Image
Feature management is an alternative to configuration keys for releasing and introduce a new features into D365FO.  MS is still releasing updates around the framework but the existing state as per 10.0.9 provide all we need to get started with releasing functionality that is controlled by the feature management framework.  The key to the feature framework is the feature class, in my example below see the class  pekTestingFeature. It is used as a descriptor for the feature and the flag to indicate if the feature is enabled or not. Once the class is created and compiled, users can navigate to Feature management  under System administration  and enabled/disable the feature. It is possible to make a feature enabled by default or disable the possibility to disable the feature. If the feature doesn't automatically appear, run the Check for updates button.   The feature class can be applied to menu items and menus. If enabled the menu item or menu will be visible to the
Read more

Continuous integration and deployment Power platform FinOps tweaking

-
Image
If you are working with the new unified development environments and CICD pipelines described here .  You might find the fact that we have to update the pipeline with the platform and application version annoying.  A quick way to get around this if you are using azure hosted agent pipeline as per this repo is to pull the number from the package.config and using it in the create deployable package task as per the two example tasks below.  The first powershell task will pull the version from the nuget files and save it to variable that can be reused in later tasks within the job. 
Read more