Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Upgrading to Ax2009 - Duplicate RECID

90 views
Skip to first unread message

Graves Kilsgaard

unread,
Sep 16, 2009, 4:26:01 AM9/16/09
to
Hi
I am running a DB upgradet from Ax30 to Ax2009, and have executed the
Duplicate Detection.
I Found some duplicate RECID's :-(
Is there anyway that i can reasign a new RECID to the fields or what is the
best practice for this problem?

Thanks on advance :-)

/Graves

/Pal

unread,
Oct 1, 2009, 3:08:01 AM10/1/09
to
Hi Graves!

Is this still a problem?
There is a solution.
In order avoid running into problems during upgrade, the Pre-Upgrade
Duplicate Detection form should be run on the Axapta 3.0 database before you
run any other upgrade scripts. The form and the related class are available
for download on Partnersource as .xpo files. You must import these files into
your Axapta 3.0 system and run the form to identify any duplicate record IDs
that exist in the database. You must resolve these duplicates beore running
any of the upgrade scripts.
Regards
/Pál

Graves Kilsgaard

unread,
Oct 1, 2009, 3:16:06 AM10/1/09
to
Hi /Pal

Yes it is a problem.
i have run the Duplicate Detection Form, and have received a list over
duplicate RecID's.
But my question is, how do i solve these errors?
Can i assign a new recid for the record or is there any best practice?

Thanks on advance :-)
/Graves

Svein F

unread,
Oct 15, 2009, 11:29:19 AM10/15/09
to
I'm afraid it's not an simple answer, du to the fact that Ax uses RefRecid to
refer to an record in 'anoter table'. You must identify witch other tables
that refer to the table with doplicates, and then take it from there.
Evaluate those spesific records....

br
Svein

Sam

unread,
Jan 4, 2010, 4:09:01 PM1/4/10
to
I have the same issue, I have about 800 duplicate cases across two companies.
AX 3.0. I see the duplicates on following tables:

CommissionTrans
InventDim
InventSerial
InventSum
InventTransPosting
LedgerBalancesDimTrans
LedgerBalancesTrans
SalesParmUpdate
TransactionLog
PurchParmUpdate


I cannot find anywhere on what is the best practice of resolving, even if
recreating a line (i.e on commissiontrans) it does not give me automatically
a new RecID, it just gives me what I have already for that! How am I supposed
to know what is the next number? And what is the best way to see if any table
from above is being referenced with any other table based on RecID field?

I appreciate any help as I am stuck on this!
Sam

Sam

unread,
Jan 5, 2010, 10:48:01 AM1/5/10
to
Here is an update what I have done to deal with fixing duplication.
Table: commissiontrans
1- I have exported transactions for the duplicated recid's (i did this by
creating a report and filtering by those id numbers'
2. I have imported to a temporay table the duplicated RecIDs
3. I have run a job that deletes rows from commissiontrans table that have
same recIDs on temptable.
4. I have imported the rows that I have deleted using the info exported on
point 1. These rows system assigns new RecIDs
5. Now when I run form for checking duplications I dont have any
duplications of RECIDs on commissiontrans table.

I am not sure if there is any other way to fix the duplications of RECIDs
but unless any tables below are linked with any other table based on RECID I
think this should work. Any help I can receive will help me a lot.

One more thing, class 'sysrecrepair' it does not fix the duplication of
RECIDs. i.e if two records had RECID 50, after it runs both records will have
some other number but still the same i.e 70!

Graves Kilsgaard

unread,
Mar 2, 2010, 3:45:01 PM3/2/10
to
Hi
Sorry for my absens, have not received notifies.

SAM: Thanks for the updates, that sounds like a way. A long one, but i have
not found any either :-(
Have tried the repair also, but no solution.
I had an idear that i would try to export and import the databases (that
have always been the solution in C5 and XAL when we had problems), but have
been stuck in some other issues (and it is going to take lots of time).

/Graves

Zbysek

unread,
Mar 8, 2010, 8:39:02 AM3/8/10
to
Is your problem a duplicate recids but having unique records itself?
If yes, you can try to do a standard AX data export and then import them
into a new comapny with the reindexing and record Id compression options.
But I'm not sure if this helps.

My only question is how did you managed to get these duplications into the
AX :-)

Zbysek

0 new messages