Advanced Considerations for Views

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes advanced considerations about view objects in Microsoft Dynamics AX.

Global Table Join to Company-specific Table Treats Both as Global

A company-specific table has its SavePerCompany property set to Yes. And it has a DataAreaId column which stores the company code. A global table has no DataAreaId column.

The first data source on a view can be a global table. The global table can be joined with a company-specific table as the second data source. In this case, the company-specific table is also treated as a global table. This treatment as global means that the view will have no DataAreaId column that is automatically added to the view by the system.


In versions prior to Microsoft Dynamics AX 2012, it was not possible to have this configuration of a global table joined by a company-specific table.

No Automatic Support of Table Inheritance for a Data Source

Views that have a derived table as their only data source do not have access to the fields that the derived table inherits from its base table. The base table can be joined as another data source to gain access to the fields of the base table.

See also

Walkthrough: Add a Computed Column to a View

View Overview

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.