Upgrade 30 SP3 NA DIS to 40 SP2 - data issues

[PvO_be]

We are in the process of upgrading our 3.0 SP3 NA DIS system directly to a
4.0 SP2 system by following the MS suggested flow chart.

The code upgrade is coming along pretty good, but we need assistance with
the data which keeps failing. The current points of failure are in the
Post-Synch of the checklist. The batch fails on the
VendConsistencyCheck_LinkTable, CustConsistsencyCheck_LinkTable and
InventMovement tasks.

We're using the AxDBUpgrade.exe tool that is provided with the original 4.01
(I think that is the version) DVD to convert the data from 3.0 to 4.0 format.
Can someone confirm that this tool does support a direct jump to 4.0 SP2.

Our initial conversion is based upon a small test dataset that we know has
some consistency check issues. So, before we upgrage the data with the
provided MS tool, should we have performed a successfull (no errors)
Consistency Check in the 3.0 system?

Thanks,

Patrick

[ReiffL]

Patrick,

You will get errors if you try to run the 3->4 data conversion on a SP2
client/AOS/application. I suggest running the entire upgrade process using
4.0 SP1 (AKA 4.01), then immediately doing the upgrade to SP2. The SP1 -> SP2
process does not take more than an hour or two.

Any custom code that you may have developed in an SP2 dev environment will
probably not affect the upgrade process, so go ahead and load all your
modifications into the live SP1 environment for the upgrade (otherwise you'll
lose your custom tables and fields during syncronization).

Good luck!

ReiffL
Dayton, OH

[PvO_be]

In the meantime we have completed various test conversions succesfully going
from 3.0 SP3 to 4.0 SP2 using the upgrade DB tool.
Not all data tests have been completed, but so far so good.
If we see any major problems, we will try your suggested multi-step approach.

Patrick

[k.Naushad]

In Microsoft Dynamcis AX Developer Center its given like this

When an object with a DEL_ prefix is introduced, the Microsoft Dynamics AX
update mechanisms handle changes in the standard application, for example by
moving fields and X++ code to the table that replaces the one with the DEL_
prefix. But if you have written X++ code that references an application
object that has been given a DEL_ prefix, you should evaluate and modify your
modifications.

Question: how do we know which object replaces a particular DEL_prefixed
object.