web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / AA violation of primar...
Microsoft Dynamics GP (Archived)

AA violation of primary key constraint/cannot insert duplicate key in object

(0) ShareShare
ReportReport
Posted on by Renee Leung 6,775

 

When trying to upload an AA budget, the following error displays "Unhandled object exception:  Violation of PRIMARY KEY constraint '___.' Cannot insert duplicate key in object "

 

 

I checked this kb article but the resolution / workaround #2 does not return values. The script may be out of date; SQL Version is SQL Server 2008 

http://support.microsoft.com/kb/897280

*This post is locked for comments

I have the same question (0)
  • Cheryl Waswick Profile Picture
    Cheryl Waswick on at
    Re: AA violation of primary key constraint/cannot insert duplicate key in object

    Table AAG00905

    This table stores the Budget Tree Account Balance. It already sees a value in this table that you are trying to import, so it is returning a duplicate record error. The primary keys on this table are: aaBudgetID, aaCodeSequence, ACTINDX, aaFiscalPeriod, aaActualPriliminary.  

    Typically to resolve, make sure you don't have the same code and account combination listed more than once within each level.  

  • Renee Leung Profile Picture
    Renee Leung 6,775 on at
    Re: AA violation of primary key constraint/cannot insert duplicate key in object

    Yes it is referencing a duplicate key for AAG00905. I updated the field in SQL based on this KB article support.microsoft.com/.../897280 but it did not resolve the error. Could you expand on the AAG00905 error, Cheryl? We checked multiple times in the budget, but it looks fine to us. Thanks!

  • Cheryl Waswick Profile Picture
    Cheryl Waswick on at
    Re: AA violation of primary key constraint/cannot insert duplicate key in object

    Does the error reference a table at all?   Usually it does and then you can see what table it is having issues with.  I have seen this happen before, and if a duplicate key on the AAG00905 is from having an account in the budget that does not exist.  An error on the AAG00904 may be due to having imported in AA dimension codes and the AAG00401 has duplicate codes....so it could be from a number of reasons.  Seeing the whole error message will give a better indication of what the issue is.

  • Renee Leung Profile Picture
    Renee Leung 6,775 on at
    Re: AA violation of primary key constraint/cannot insert duplicate key in object

    Yes we checked for duplicates and did not see any. The same error message appears at the point where budget upload is 'waiting for SQL Server'

  • Verified answer
    Richard Whaley Profile Picture
    Richard Whaley 25,195 on at
    Re: AA violation of primary key constraint/cannot insert duplicate key in object

    check your source file for lines with duplicates of the following fields:

    Budget ID + Code Sequence + Account +Period Date + Fiscal Period

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans