Skip to main content

How to access other data in other company accounts in Axapta / Cross Company

First of all we have to understand the concept of Axapta, that one AOS (Application Object Service) of Axapta can have many company accounts, one AOS can be described as one Group of company, and each company accounts in Axapta can be described as sub ordinary of the company group. Just say one group company who implemented Axapta wants to put all their sub ordinary company to one AOS, that mean we have to setup the parameter so that can have more than one company accounts, each company accounts can have their own setup parameters.

There is one feature in Dynamics Ax 2009 which is can access other data in other company accounts through the code or through Data Source object, we called it cross company.
For example cross company in DataSource. Each Form or Report object have DataSource to pull the data into it. We can add Table/Query object as DataSource or we can call them at runtime.
This is the example how to setup the DataSource to enable the cross company feature below :


This is the example how to setup the DataSource through the code. What you see is that we setup the cross company through query variable that pull the data from DataSource :
There is one DataSource "InventTable".
public boolean fetch()
{
Query qry = new Query();
QueryRun qr;
QueryBuildDataSource queryBuildDataSource;
;

queryBuildDataSource = qry.addDataSource(tableNum(InventTable));
qr = new queryrun(qry);
qr.allowCrossCompany(true);//true means that the object allowed cross company, false means didn't allowed cross company
while (qr.next())
{
........
}
}
This is the example how to pull the data through syntax query :
"Select crosscompany : companyList InventTable;"
InventTable is one of the table in Axapta
companyList is container variable that kept the list of company accounts that allowed to be access.
Labels:

Popular posts from this blog

Mark All for Open Cust Trans and Open Vend Trans

We have situations where there are lots of open transactions that need to be settled against each other. This can be the case if auto settlement is turned off. One solution is to add a "Mark All" button to the custOpenTrans or vendOpenTrans forms. This button "checks" the mark checkbox on every line. The user can then uncheck several lines if needed and Update to settle the lines. The code below is an example of what we used on the open vendor transaction screen. The code is very similar on the AR side. One note: I used vendTable.AccountNum in the code below. That should be generalized to work with any buffer that is passed into the open trans form. void customMarkAll() { VendTransOpen localVendTransOpen; VendTrans localVendTrans; container conSum; int linesProcessed; ; //show wait cursor startLengthyOperation(); element.lock(); //remove all prior markings specOffsetVoucher.deleteSpe...
Read more

Print Report in Microsoft Dynamics AX 2009 through X++

I am trying to print sales confirmation report on a button click which I have added on Sales Order Detail form in Microsoft Dynamics AX 2009. On click event of that button, I have written following code: void clicked() {     Args                args;     ReportRun           reportRun;     SalesFormLetter     salesFormLetter;     PrintJobSettings    printJobSettings;     CustConfirmJour     custConfirmJour;     RecordSortedList    list                = new RecordSortedList(55);     SalesTable          salesTableUpdate;     ;     SELEC...
Read more

Creating Free Text Invoice through X++ code

Job: Calling class from job to run the class public void freeTextInvoicePostTestJob() { Dialog dialog; DialogField dlgCustAcc; DialogGroup dialogPeriodLengthGroup, dialogPeriodLengthGroup1; DialogField dlgLedgerAcc; ; dialog = new Dialog("Free-Text Invoice"); dialogPeriodLengthGroup1 = dialog.addGroup('Cust Table'); dlgCustAcc = dialog.addField(typeid(CustAccount)); dialogPeriodLengthGroup = dialog.addGroup('Ledger Table'); dlgLedgerAcc = dialog.addField(typeid(LedgerAccount)); if(dialog.run()) { if(dlgCustAcc.value() && dlgLedgerAcc.value() != '') FreeTxtInvoiceCreatePost::main(dlgCustAcc.value(), dlgLedgerAcc.value()); else throw error(strfmt("Either CustAccount or LedgerAccount info is missing.")); } } Class: Which creates the free text invoice class FreeTxtInvoiceCreatePost { } static void main(CustAccount _custAccount, LedgerAccount _ledgerAccount) { CustInvoiceTable custInvoiceTable; ...
Read more