Thanks David I am not 100% sure as the programmer did the upgrade but for now I would have to assume yes it was done (I will check) If they did not run this job do you know the effect? Does this process just change the field type into Int64? or does some renumbering of recid? The SQL type is Int64 in the database Thanks James
_____ From: development-axapta@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of david santoso Sent: 24 August 2008 17:24 To: development-axapta@yahoogroups.com Subject: Re: [development-axapta] Serious Recid problems Hi James, Did you notice that when you upgrade from ax 3.0 SP4 into ax 4.0, you have to run the upgrade column list 9 the purpose to change the recid into int64. My company has upgrade from 2.5 -> 3.0 SP 6 -> 4.0 SP2 for 1 month, and has run the posting confirm smoothly. Cheers, David S On Fri, Aug 22, 2008 at 5:18 PM, James Flavell <[EMAIL PROTECTED] <mailto:djf1994%40gmail.com> com> wrote: > Hi everyone, somethign interesting to share and praying someone might > have > some ideas of how to fix or investigate further: > > In the SalesTable form in the active method for Salestable datasource there > is code that checks whether the Functions button on the header should be > enabled. > > We have the situation that this code returns False even though there is a > RecId for some salestables. We found the KB 930416 which mentions about > similar problem but we have the required hotfix/build and are still getting > a problem. > > What we noticed was if we convert salestable.recid to a boolean first and > then test this it is okay but not if we just do enabled(salestable.recid) > > This does not work: > buttonHeaderFunction.enabled (salesTable.RecId); ->change boolean > > This works (htktestbol is of type boolean): > htktestbol = (salestable.recid); > buttonHeaderFunction.enabled (htktestbol); > > The salestable record having the problem is having a recid value that is a > BigInt (i.e. the recid is too large to fit in an Int) > > We have one more problem that has also appeared and that is for certain > inserts such as posting of order confirmation we get an SQL error (see > below) we are wondering is this also due to the recid not testing as true!? > > SQL error: > Cannot create a record in Confirmation journal (CustConfirmJour). Order > Confirmation: , 20016. The SQL database has issued an error. > operation cancelled > An error occurred durign update > > This error can happen on various tables not just Confirmation journal. > > We tested and found the following results. If we do an AX def export of the > company and then imported into a new company: > 1) if we import in to the same SQL database but just a new company the > problem still happens in the new company > > 2) if we import into a clean SQL database there is no problem > > To us this suggest some issue with RecId (and maybe SystemSequence table or > something that is shared across all companies?) > > Note this is an Ax3.0 SP4 upgraded to Ax4.0 > > Thanks > James > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
