Build numbers
Here the Axapta build numbers,
Client versions
Build number Version AOCP version
1951.8 3.0 N/A
1951.17 3.0 SP1 60029 (0xEA7D)
1951.18 3.0 SP1 N/A
1951.2410 3.0 SP2 60031 (0xEA7F)
1951.2411 3.0 SP2 Hotfixed 60031 (0xEA7F)
1951.3730 3.0 SP3 60031 (0xEA7F)
1951.3733 3.0 SP3 Hotfixed 60031 (0xEA7F)
1951.4060 3.0 SP4 60031 (0xEA7F)
1951.5160 3.0 SP5 61031 (0xEE67)
1951.6710 3.0 Kernel Rollup 1 61031 (0xEE67)
1951.7500 3.0 Kernel Rollup 2 63031 (0xF637)
1951.7609 3.0 Kernel Rollup 3 63031 (0xF637)
Application versions
Build number Version
514-90 3.0 SP2
514-193 3.0 SP3
514-320 3.0 SP4
514-513 3.0 SP5
514-859 3.0 SP6
Dynamics AX Version 4.0
Build number Version AOCP version
4.0.1659.26 4.0 RTM 41638 (0xA2A6)
4.0.1659.35 4.0 RTM (localized) N/A
4.0.2163.0 4.0 SP1 42060 (0xA44C)
4.0.2500.XXX 4.0 SP1 DIS layer hotfixes 42060 (0xA44C)
4.0.2501.116 4.0 SP2 42060 (0xA44C)
4.0.2503.XXX 4.0 SP2 DIS layer hotfixes 42060 (0xA44C)
[edit] Dynamics Ax 2009
Build number Version
5.0.593.0 2009 RTM
5.0.1000.52 2009 SP1
[edit] See also
Monday 15 June 2009
Subscribe to:
Posts (Atom)
Update NuGet package to new MS D365FO version
1. Import the NuGet package files from LCS for that particular version please take the PU version files only. a. Goto LCS-->Asset Libra...
-
In the below example we will see how we can get the default financial dimension values from Purch line table. Here we are using AxdDimensi...
-
Here we are going to see how we can filter / override the lookup on the form control. Scenario, we need to override the TemplateID lookup... -
It is very common to use Like Operator in SQL SELECT column1, column2, ... FROM table_name WHERE columnN LIKE pattern ; N...