Yup did that as well...
On Tue, Mar 17, 2009 at 6:24 PM, MaryAnn Hand <maryann.h...@gmail.com>wrote: > 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<loya.sumit%40gmail.com>> > wrote: > > 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 the data back to SysDataBaseLog from old DB > > through SQL. That is when I faced this problem through SQL as well. > Database > > log setup is restored but not the SysDataBaseLog. > > > > Have worked on a couple of upgrades but did not face this kind of > problem. > > > > What amuses me is that though i am changing the property of createdDate > it > > is still reverting back to original settings... :) > > > > Regards, > > Sumit > > > > On Mon, Mar 16, 2009 at 9:18 PM, MaryAnn Hand > > <maryann.h...@gmail.com<maryann.hand%40gmail.com> > > > > wrote: > >> > >> 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 can be restored by SQL updates after > >> upgrade. > >> > >> I would not ever use a backend script to insert into AX tables - AX > >> needs to generate the RecIDs! You can write a job in the AX 2009 > >> environment to read from ODBC connection to old database and write > >> records to the new database. I suggest you use the appropriate > >> AX<table> class to do the record creation. > >> > >> On Mon, Mar 16, 2009 at 9:30 AM, Sumit Loya > >> <loya.su...@gmail.com<loya.sumit%40gmail.com>> > wrote: > >> > 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],[TABLE_],[LOGRECID],[CREATEDDATETIME],[DEL_CREATEDTIME],[CREATEDBY] > >> > ,[CREATEDTRANSACTIONID],[DATAAREAID],[RECVERSION],[RECID]) (SELECT > >> > [DESCRIPTION],[LOGTYPE],[DATA],[TABLE_],[LOGRECID],[CREATEDDATE] > >> > > >> > > ,[CREATEDTIME],[CREATEDBY],[CREATEDTRANSACTIONID],[DATAAREAID],[RECVERSION],[RECID] > >> > FROM [AX40ProdDB].[dbo].[SYSDATABASELOG]) > >> > When we run this script it throws up an error "Invalid column name > >> > 'createddate'...". > >> > > >> > Currently we had to delete all the SysDataBaseLog records and remove > all > >> > database log setup to upgrade. > >> > > >> > Dont know if this is a problem with standard AX? > >> > > >> > Regards, > >> > Sumit > >> > On Sat, Mar 14, 2009 at 3:16 AM, MaryAnn Hand > >> > <maryann.h...@gmail.com<maryann.hand%40gmail.com> > > > >> > wrote: > >> >> > >> >> 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 workaround anyway. > >> >> > >> >> On Fri, Mar 13, 2009 at 9:36 AM, Sumit Loya > >> >> <loya.su...@gmail.com<loya.sumit%40gmail.com> > > > >> >> wrote: > >> >> > 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)): > >> >> > [Microsoft][SQL > >> >> > Native Client][SQL Server]Invalid column name 'createddate'.. The > SQL > >> >> > statement was: "INSERT INTO SYSDATABASELOG > >> >> > > >> >> > > >> >> > > (DATA,USERNAME,DESCRIPTION,LOGTYPE,TABLE_,LOGRECID,CREATEDBY,CREATEDTRANSACTIONID,DATAAREAID,RECVERSION,RECID) > >> >> > VALUES (?,?,?,?,?,?,?,?,?,?,?);SELECT CREATEDDATETIME FROM > >> >> > SYSDATABASELOG > >> >> > WHERE RECID = ? AND DATAAREAID = ?" > >> >> > > >> >> > > >> >> > > >> >> > This error is thrown when HRMApplicantTable is getting updated from > >> >> > HRMVirtualNetworkTable. > >> >> > > >> >> > > >> >> > > >> >> > I know MS has changed all the createdDates to createdDateTime in AX > >> >> > 2009. > >> >> > But dont know why AX keeps throwing this error of Invalid column > >> >> > name. > >> >> > > >> >> > > >> >> > > >> >> > Has anybody else encountered this problem during upgrade? > >> >> > > >> >> > > >> >> > > >> >> > Regards, > >> >> > > >> >> > Sumit > >> >> > > >> >> > > >> > > >> > > > > > > > >
