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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / CompanyInfo table move...
Microsoft Dynamics AX (Archived)

CompanyInfo table moved in AX 2012 R2 - table inheritance implementation changed?

(1) ShareShare
ReportReport
Posted on by Roy Wallace 35

Hi,

In AX 2012 R2 databases, it appears that the CompanyInfo table (for example) exists in the AOT but not in the actual SQL database. The columns & data that are supposedly contained in CompanyInfo (according to the AOT) are actually found in the DirPartyTable. This is in contrast to AX 2012 databases.

Is this a consequence of table inheritance being implemented differently in AX 2012 R2, compared to AX 2012? The reason I ask is that I notice that by browsing the CompanyInfo table in the AOT and observing its "Extends" property, I can trace the inheritance tree back to DirPartyTable. As mentioned in the MSDN article Selecting Data from a Table Inheritance Hierarchy, "The physical implementation of table inheritance in the underlying Microsoft SQL Server database might vary between versions of Microsoft Dynamics AX."

Has anyone else run into problems with these apparent changes?

Thanks,

Roy

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Joris dG Profile Picture
    Joris dG 17,775 on at

    You're correct. Martin Drab actually has a nice article about this on his blog dev.goshoom.net/.../queries-to-tables-with-inheritance

    Of course the question has to be asked, why are you selecting things in the database directly, except for educational purposes. I strongly recommend using services instead.

  • Community Member Profile Picture
    Community Member on at

    My last message was removed so I'll just respond to your question Joris:  The reason people select things directly in the database is because learning how to do it within AX can be very complicated to learn, especially with the HR/Payroll modules.

  • Thierry Lach Profile Picture
    Thierry Lach on at

    Another reason is for production support.  Developers should not have access to the AOT in production environments, so doing database queries is sometimes the only way to examine the data.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans