Cross-Company and the company Getter Method

Artigo
05/18/2015

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

The dataAreaId value returned by the company getter method on table buffer variables can differ between cross-company versus single-company scenarios.

For information about how a table buffer variable inherits company from the xRecord class, see Cross-Company Methods and Properties.

Tables can be categorized into the following types:

Global - The SaveDataPerCompany property is set to No.
Company-specific - The SaveDataPerCompany property is set to Yes.
Shared - Company-specific tables associated with a virtual company.

These different types of tables interact differently with the cross-company feature. In cross-company scenarios, the current company can be different from the company of the row currently being processed by the application X++ code. This difference has implications for the company getter method.

Note

The current company (the user's session company) is shown in the status bar in the lower-right portion of the Microsoft Dynamics AX client window.

Global Tables and the company Method

For a table buffer variable declared from a global table, the company getter method returns the user's session company. Global tables do not have the field named dataAreaId.

Company-Specific Tables and the company Method

A table buffer variable declared from a company-specific table can be populated by a while select crossCompany statement. This populates the buffer with rows that represent a variety of companies. When a buffer is populated in this manner, the company method returns the dataAreaId value of the buffer's current row, regardless of the user's session company.

Shared Tables and the company Method

For some rows in a shared table, the dataAreaId field can have a value representing the virtual company that the table is associated with. Other rows can have dataAreaId values for real companies that are outside of the virtual company.

The following X++ code example populates the table buffer with a row set from a shared table that has both kinds of dataAreaId values.

    while select crossCompany * from SH_buffer { /* X++ */ }

The following descriptions assume that the shared table is associated with virtual company VC9. The descriptions assume that VC9 is associated with real companies CM1 and CM2.

During the while select loop that processes rows of each dataAreaId value, the company getter method on the table buffer returns values according to the following table.

Test case number	dataAreaId in shared table's current row	Current session company	Returned by company getter method
1	VC9	CM1	CM1
2	VC9	CM2	CM2
3	VC9	CM3	Either CM1 or CM2, whichever the user has greater permissions on. For example, Delete permission is greater than Read permission.
4	CM3	(Any company)	CM3

Note

In Microsoft Dynamics AX 2009 the above table describes the behavior when either a table or a view is the subject of the while select. In the previous version, it applied to tables but not to views.

Rules Governing the company Method

The following rules govern the behavior of the company getter method of table buffer objects:

The session company can never be a virtual company.
The company method never returns a value that conflicts with the dataAreaId of the current row. The dataAreaId takes precedence over the session company.
The company method never returns the dataAreaId value of a virtual company. Instead, a real company in the virtual company is returned.
When the current row has the dataAreaId of a virtual company, the company method returns one of the real companies in the virtual company.
After the clear method is called on a table buffer, the company getter method retrieves the current company of the client. However, this is not true for temporary tables.

Greater Permissions Factor for Test Case 3

Test case number 3 in the preceding table shows that sometimes the system chooses which real company to return when the company method is called. In cases where the session company is not part of the current row's virtual company, the company method returns whichever real company the user has the most permissions for.

In test case 3, if the user has both read and insert permission for CM1, but only read permission for CM2, then CM1 is returned.

The system determines which real company the user has greater permissions for only when the session company is not in the virtual company.

Compartilhar via