Code and technical differences between AX 3.0 and 2009

-
During a upgrade from AX 3.0 and 2009 i discovered that many of the classes no longer exists in AX 2009 or have been divided into several subclasses.

Here are some things that are good to know.

- The Forms are considerd as a whole object by ax which replaces all functionallity in 2009 by 3.0 functions and looks if you dont implement the changes manually.

- The new method in AX 3.0 have been replaced with static functions that are called "construct" in 2009.

- (3.0 Class)Specification is replaced by (2009 Class)SpecTransManager

- LedgerJournal.newJournalNum(true); is done with a call to the static function NumberSeq::newGetNum(LedgerParameters::numRefJournalNum(), true).num();

- NumberSeq::newGetVoucherFromCode(voucherSequence) is a new way of getting the voucher instead of using LedjerJournal. NumberSeq also contains other static functions for this with different paramters.

- LedgerJournal.usedVoucher(); is done with a call to NumberSeq::newGetVoucherFromCode(voucherSequence).used();

- The field RefId is replaced by RefRecId.

- The call to LedgerJournalTrans::journalBalanceMST(TmpLedgerJournalTable.journalNum); is done by LedgerJournalTable::journalBalanceMST(TmpLedgerJournalTable.journalNum) in 2009.

- Some functions require the current company as parameter, this can be extracted by using CurExt().

- In AX 3.0 the name of each employee is stored in EmplTable. This has been moved to the DirPartyTable. Use PartyId to join and extract the name of a employee.

- Menues that have been modified in 3.0 and transferd to a 2009 installtion will lose its icon. To restore the 2009 icon manually readd the menu modifications.

- AX standard tables that have been modified in AX 3 will loose their properties, delete actions etc. they all have to be restored manually to ensure that the field ids are not changed.

- AX standard enums that have been modified in AX 3 will be shaded by the AX 3 values. To restore the new values remove the modifications and readd the values that was added in AX 3. IMPORTANT! The change will not change the values in tables hence if this is done it is necessary to edit all the posts in tables.

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