I am also surprised that the table would revert back for former properties.
After you set the property, did you compile and synchronize?
On Mon, Mar 16, 2009 at 11:34 PM, Sumit Loya loya.su...@gmail.com wrote:
Hi,
This is what exactly we did..
Though we tried to set the createdDate property
Yup did that as well...
On Tue, Mar 17, 2009 at 6:24 PM, MaryAnn Hand maryann.h...@gmail.comwrote:
I am also surprised that the table would revert back for former
properties.
After you set the property, did you compile and synchronize?
On Mon, Mar 16, 2009 at 11:34 PM, Sumit Loya
Hi,
Still the problem is not solved.
We tried to copy data from AX 4.0 to AX 2009 using a backend script on the
table but it throws error there itself.
Here is the SQL Script
INSERT INTO [AX2009DB].[DBO].[SYSDATABASELOG]([DESCRIPTION],[LOGTYPE],[DATA]
If there are no customizations involved in this upgrade, then you
should submit this issue to Microsoft for investigation. I have done
multiple 4.0 upgrades to AX 2009. When I encountered problems with
createdDate I removed that field by modifying the property. Then
upgraded the data. The dates
Hi,
This is what exactly we did..
Though we tried to set the createdDate property to No it was still restoring
it back to Yes. Strange though..
So we just deleted the SysDataBaseLog records from AX 2009 and Databse Log
Setup from AX2009 and went ahead with upgrade.
After that We tried copying
Hi All,
I am working on upgrading a AX 4.0 SP2 application to AX 2009 SP1.
While running Post synchronization in data upgrade I am encountering an
error in job updateHRMVirtualNetworkTable.
Here is the error from event viewer.
Object Server 02: The database reported (session 6 (AnAg)):
In the 4.0 environment, go to the properties of that table and make
sure that the createdDate parameter is set to NO. This will delete
the createdDate field and then your upgrade will work without that
error. I agree that the upgrade should be smarter than it is - but
what I suggest is a
7 matches
Mail list logo
