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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Adding new field in DirPartyTable throws SQL synchronization error

(0) ShareShare
ReportReport
Posted on by 720

Hi All,

I am unable to add new fields to DirPartyTable in AX 2012. When I save/open the table after creating the new field it throws some SQL synchronization error. I tried synchronizing the table but the error still persists.

Can anyone here help me to fix this. Thanks in Advance

/Imran

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,882 Most Valuable Professional on at

    Could you tell us more about the "some" error?

  • MukeshHirwani Profile Picture
    1,180 on at

    Hi Azami,

    what kind of fields you want to add to DirPartyTable..? And what is d error while adding?

  • Tommy Skaue Profile Picture
    Moderator on at

    The DirPartyTable is inheritable, so if you were to add a column with a name equal to one of the columns in the child tables (the ones inheriting DirPartyTable - like DirPerson), then it will fail.

    What column are you trying to add to DirPartyTable?

  • Imran Azami Profile Picture
    720 on at

    Hi,

    Apologies for not being clear in my earlier post. I am trying to create a new field of type Int64 in DirPartyTable. When I do that, the table synchronizes and throws the following errors.

    "Cannot create a record in Global Address book (DirPartyTable). The SQL database has issued an error"

    "SQL error description: [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid Column name "INTERNALPHONE"."

    InternalPhone is my field name.

    Synchronizing the table also throws the same error.

    I am unable to open the table through table browser, or any form which has DirPartyTable under its datasource node.

    I am working in AX 2012 R2. I tried in different installations of R2, but same result. 

    I tried the same in R1, it worked there. It seems the problem is in R2.

    /Azami

  • Tommy Skaue Profile Picture
    Moderator on at

    Can you head over to the database and have a look at the DIRPARTYTABLE itself? It sounds like the field is already there.

  • Martin Dráb Profile Picture
    237,882 Most Valuable Professional on at

    It behaves in the same way in my AX2012 R2. I don't see what's wrong - it works for fields with other names, InternalPhone doesn't exists in table hierarchy and I can add column directly in database without problems.

    I don't have time to investigate it right now, but I would really like to understand it - I'll take a look later.

  • Imran Azami Profile Picture
    720 on at

    Hi Martin and Tommy,

    Thanks for replying.

    I checked DB, the field isn't there. The real problem is the table stops synchronizing with DB immediately after creating the new field.

    Its really strange. I have reported the same Issue to one of the AX Dev team member at Microsoft and awaiting reply.

    Meanwhile, I too will try to investigate and post it back here if I find any solution.

    /Azami

  • Martin Dráb Profile Picture
    237,882 Most Valuable Professional on at

    I tried to add the field and synchronize DB with SQL Server Profiler running and it seems that no synchronization command is sent by AX, so something must be wrong in AX application logic. I think this needs to be resolved by Microsoft engineers, nevertheless they shouldn't have troubles to reproduce it - I managed to reproduce it in several distinct environments.

  • Tommy Skaue Profile Picture
    Moderator on at

    Wow. I'm at loss for words. Perhaps "INTERNALPHONE" is some weird Easter Egg? ;-)

    Good catch, Martin.

  • Imran Azami Profile Picture
    720 on at

    Good work Martin :).

    And, its not only InternalPhone I am unable to add any field to DirPartyTable and I think its because I tried first with Internalphone, so it throws the same error even when creating fields with different types and names later on.

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

Quick Links

Responsible AI policies

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

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
Sukrut Parab Profile Picture

Sukrut Parab 2 Moderator

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans