RecId
From Axaptapedia
The RecId is a unique field in every table, used as an identifier. Every row in the system can be guaranteed (in theory) to have a unique RecId. RecIds can be negative, and their value can change due import/export operations. Due to this, it is not a good idea to use RecIds as foreign key references to other tables.
If RecId corruption occurs, the SysRecIdRepair can be used to corect the problems. Axapta uses SystemSequences table to store urrent value of RecID (see http://www.eggheadcafe.com/forumarchives/axaptaprogramming/Aug2005/post23243136.asp)
[edit] Additional information
The following is cited from Axapta Knowledge Village
Try running the SysRecIdRepair class in the AOT, It takes a long time to run but will clean it up significantly.
--- In Axapta-Knowledge-Village@yahoogroups.com, "lourens1210"
<lourensjb@t...> wrote:
Can anybody shed some light urgently please!!
We have a very young Axapta installation and have found that the recid's are already running negative and is being allocated towards Zero. This raises a few questions:
- What can cause the positive id's to be 'used up' already?
- If the recid's are not 'used up' what can cause the sign switch so early on in the life of the database (Apparently once the maximum positive number have been reached: 2,176,xxx,xxx, axapta goes to maximum negative and create from there - it does not seem likely that we have exhausted the positive numbers already)
- Is it normal for recid's to be allocated not strictly in sequence?
- What happens when the recid series reaches Zero?
- If this situation is abnormal how do we correct it?
Thanx everybody
