You can run a job to display the tableId in infolog.Ģ. You can find the tableId from AOT, under Properties for the table.ī. Steps to resolve the error 'record already exists':Ī. NextVal field should be set to a value greater than the max RecId of the table. To fix this error, we need to reset the NextVal field in SystemSequences table. There has been tableId conflicts during model store move Data is inserted in the SQL database directlyĢ. The RecId sequence for tables is stored in SystemSequences table and can get out of sync due to one/more of the following reasons:ġ. I verified all the unique index requirements were satisfied and there were no duplicated index values.Īfter investigating, I found out that the RecId generated by the system was getting a value that has been previously used. One of the most common reasons for this error is, one of the unique index fields has duplicated value. I was recently working on an issue in Dynamics AX where, after a code move we started receiving the error: ‘Cannot create a record in "TableName." The record already exists.’ Diversity, Equity, Inclusion & Belonging.Dynamics GP to Dynamics 365 Business Central. Dynamics NAV to Dynamics 365 Business Central.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |