Dynamics Ax Virtual Company & Table Collections

This article describes how Dynamics Ax Virtual Company and Table Collection work. We will also
discuss how to move data from normal company to virtual company when you introduce virtual 
company in existing Ax implementation.

Virtual Company:
Dynamics Ax stores data as per company in tables. But there might be occasions when you want to
share data across companies, like country, state, zip codes data. This sharing of data is achieved by 
creating a virtual company and storing data in this virtual company. Normal companies are then 
configured to read/write data from this virtual company. The only purpose of virtual company is to 
share data across companies, you cannot log into this virtual company.

Before seeing how to do virtual company setup, I would like you to show another trick that can be
used to share data across Ax. There is a property on Ax tables called "SaveDataPerCompany", 
you can use this property to save data globally in Ax. To share data set this property to "No".

Note: This data is shared by all the companies in Ax. This option will delete DataAreaId field and 

default (DataAreaId, RecId) index from the table. If you want more control on shared data, like

which companies can share and which can not then use virtual company. 

Virtual Company setup:

Step 1: Create Table Collection

Decide which tables you want to share and create a table collection for these functionally related tables.

For example; if you want to share Global Address Book across companies then you can utilize the 

existing table collection "DirPartyCollection".

To create a table collection, go to AOT\Data Dictionary\Table Collections and on right click select 

"New Table Collection", then just drag your required tables in this collection.

Step 2: Create Virtual Company, configure/attach normal 

companies and table collection

Create a virtual company that will hold the shared data for normal companies.
Note: Before doing the below steps, make sure you are the Ax administrator and the only user online.

Go to Administration -- Setup -- Virtual company accounts, and create a virtual company.

Decide which companies needs to share data and attach those normal companies with this virtual
company.

Attach the table collection with this virtual company.

Your Ax client will re-start and you are done with setting up the virtual company account.

Now, when you have virtual company in place, all new data will be saved in this virtual company.

Only companies attached to the virtual company can use this shared data. All other companies which

are not attached will work normally, these companies will continue to read/write data as per company 

bases.

How to move existing data to virtual company?

When you setup a new virtual company, Ax does not move data automatically from normal company to 

virtual company. This is done by system administrator manually.

There are many ways to do this data move, but I will discuss only two approaches here.

Ax Import / Export:
This is standard Ax approach.

1. Manually export existing normal company data from Ax.
2. Remove duplicate records from this exported data set. 
3. Delete exported data from normal companies.
4. Import the exported data back in Ax, while logged into one of the participating companies. 
5. Create records deleted in point 2 again in Ax using your logic. How you want to handle duplicate? 

For example, if you have customer 'Rah' in more than one normal company, what you want to do with this?

Direct SQL:

Use this approach if you have good knowledge about SQL queries and Ax table structures/relationships.

Below are few points that will help you understand what to do and how to do.

• All Ax tables store data as per company unless otherwise specified. For this, Ax uses a special field

       called DataAreaId. In case of virtual company, it does not matter from which normal company you 

       log-in, it is always the virtual company id which is stored in DataAreaId field of shared tables. 

• Ax also assigns a unique 64bit number to each record in table. For this, Ax uses a special field called 

       RecId. This RecId is unique in the table and is generated by Ax when you insert a new record in Ax. 

       It is not related to DataAreaId / Company.

• For unique records between all participating normal companies, update the DataAreaId to the 

        virtual company id.

• For duplicate records, create them again in Ax using some Ax job or Ax import/export technique.

Attached below are some SQL queries that might help you moving the Global Address Book records from 

normal companies to the virtual company by changing the DataAreaId.

Creating a Custom Inbound AIF Service in Microsoft Dynamics AX 2012

Overview

Application Integration Framework (AIF) services are used to communicate with external systems or applications. Microsoft Dynamics AX 2012 has the following types of services:

1. Document services
2. Custom services
3. System services

An AIF service can be Inbound or Outbound. An Inbound service is used when you want to send data to an external system and Outbound services are used when you want to retrieve data. This tutorial will guide you in creating Custom Inbound AIF services in Microsoft Dynamics AX 2012. Custom services are used when:

1. The complexity of the entities is relatively low.
2. When you want to have full control of the service contract.
3. When data contracts needs to be shared with different entities.

Pre-requisites

1. Microsoft Dynamics AX 2012
2. AIF services must be installed and configured on IIS

Important Concepts

1. Service operation

   Service operations are class methods that expose any business logic in a service. To define a service operation, add theSysEntryPointAttribute attribute at the top of a method. Any existing method can be converted to a service operation by adding this attribute at the beginning of the method. 
   &absp;
   Note: The service operation name cannot include Create, Find, Update or Delete. These names are reserved to be used by AIF Document services. AX will make an exception when they are called from a client.

2. SysEntryPointAttribute

   SysEntryPointAttribute defines the authorization checks that will be performed when a method is called from the server. This attribute must be set on all the service operations. If the value is “true”, it means that authorization checks will be performed for all the tables accessed in the method and if set to “false”, no authorization checks will be performed.

3. AifCollectionTypeAttribute

   AifCollectionTypeAttribute is used when you want to use a collection as a return type or in a parameter of a service operation. This attribute defines the type of data a collection contains.

Scenario

As part of this tutorial the service will return the list of customer names in Dynamics AX.

Steps

1. First we will create a new class which will contain Service operations.


2. Open AOT. Go to Classes and create a new class. Let’s name it CustomerServiceDemo.


3. Set the RunOn property of the class to Server. This will make sure the class always executes on the server.
 
 
4. Add a new method and name it as getCustomerNameList. This method will query customers’ names and return a Type list string. Write the following code in the method:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

[SysEntryPointAttribute(true), AifCollectionTypeAttribute('return', Types::String)] //return denotes the parameter type and String specifies the type of data the collection will hold public List getCustomerNameList() {           CustTable       custTable;         List list = new List(Types::String);              //select all customers     while select * from custTable             {         //add customer name in the list         list.addEnd(custTable.name());     }          return list; }

5. The SysEntryPointAttribute tells AX that this method is a service operation method.


6. Now we will create a new service and add the above created service operation to it.


7. Go to Services, right click and select New Service.



8. Name it as CustomerServiceDemo.


9. Open the properties of the newly created service and select the CustomerServiceDemo class in the Class field.



10. Now expand the CustomerServiceDemo service node and add a new Operation by right clicking on Operations and selectingAdd Operation.



11. All service operations present in the class will be listed. Select the getCustomerNameList service operation by checking the Addfield in the grid and press OK.



12. The next step is to create a service group and deploy the service to the Inbound Port.


13. Go to Service Groups, right click and select New Service group.



14. Name it as CustomerServiceDemoGroup.


15. Set the AutoDeploy to Yes (Service will start automatically when AOS is started) and set the Description as Customer name service.



16. Right click the newly created service group and select New Service Node Reference.



17. In the newly created service node, set the Service property to CustomerServiceDemo. The Name property will automatically default to the Service name.



18. Now right click the service group and select Deploy Service Group.



19. A success message will appear if the service group is successfully deployed.


20. To verify it, go to System administration à Setup à Services and Application Integration Framework à Inbound ports.


21. The Service group name CustomerServiceDemoGroup will appear here as Port name with a green check mark. This shows that service group is deployed and active. If a red ‘x’ is appearing, select Activate from the action pane to activate the port.



22. The WSDL URI is the URL of the service which can be used by external systems to access the service.


23. To test whether the service is running properly, open the Visual Studio Command Prompt by going to All Programs à Microsoft Visual Studio 2010 à Visual Studio Tools à Visual Studio Command Prompt.


24. Write wcftestclient and press enter. WCF Test Client will open.


25. Now, go to File àAdd Service.



26. In the Add Service dialog box, paste the WSDL URI of the port and press OK.



27. The WCF Test Client will open the service with the list of operations available.


28. Double click the getCustomerNameList. It will open the operation details in the right hand side pane.



29. Click the Invoke button. The result of the service will appear in the Response pane.



30. Pat yourself on the back. You are finished!

Filter sales order in listpage salesorder num using modified method for stringedit Field in form

public boolean modified()
{
   boolean ret;

   ret = super();
  SalesTable_ds.queryBuildDataSource().clearRanges();
   if (this.valueStr() != '' )
   {
       SalesTable_ds.queryBuildDataSource().addRange(fieldNum(salestable, salesid)).value(this.valueStr());
       SalesTable_ds.executeQuery();
   }

   else
   {
       SalesTable_ds.queryBuildDataSource().addRange(fieldNum(salestable, RecId)).value("0");
       SalesTable_ds.executeQuery();
   }

   return ret;
}

Make ListPage grid Empty initiallly when opens sales orders

Go to

AOT Classes/Salestablelistpageinteraction/initializeQuery

1) This method is for automatically loaded grid records in listpage.
2) Write Else code part which mention in Blue colour for make grid empty initially.

public void initializeQuery(Query _query)
{
   QueryBuildDataSource    qbds;
   ProjInvoiceTable        projInvoiceTable;

   if (isCustomer)
   {
       EPQuery::makeMyCustomerSelfServiceQuery(_query,tableNum(SalesTable));
   }

   if (this.listPage().listPageArgs() &&
       this.listPage().listPageArgs().externalRecord() &&
       this.listPage().listPageArgs().menuItemName() ==  menuitemDisplayStr(SalesTableListPage_Proj) &&
       this.listPage().listPageArgs().externalRecord().TableId == tableNum(ProjInvoiceTable))
   {
       projInvoiceTable = this.listPage().listPageArgs().externalRecord();
       qbds = _query.dataSourceTable(tableNum(SalesTable)).addDataSource(tableNum(ProjTable));
       qbds.relations(true);
       qbds.joinMode(JoinMode::ExistsJoin);
       qbds.addRange(fieldNum(ProjTable,ProjInvoiceProjId)).value(queryValue(projInvoiceTable.ProjInvoiceProjId));
   }
   else
   {
       _query.dataSourceTable(tableNum(SalesTable)).addRange(fieldNum(SalesTable, SalesId)).value(SysQuery::valueEmptyString());
   }

   super(_query);
}

Lookups in Ax 2012

Guys check this link you will get complete knowledge on lookup in ax 2012

http://www.slideshare.net/MAnasKhan/microsoft-dynamics-ax-lookups

Container Data Type in AX 2012

Introduction

Container is a one of the data type in ax. We can hold more primitive data type values in a single container. Container index starts by 1 not 0. For example:

container   c = ['Test', 27];

info(strFmt('%1 - %2', conPeek(c, 1), conPeek(c, 2)));

Result: Test – 27

Table Field Type:

Container is one of the table field data type. So, we can store the container directly in to the database table field. In SQL, container table field data type is treated as varbinary datatype field.

Store container in another container:

We can also store one container in another container. For example:

int         i;

container   c = ['Test', 27], d = ['Second'];   

c += d;

   

for(i = 1; i <= conLen(c); i++)

{

    info(strFmt('%1', conPeek(c, i)));

}

Result:

Test

27

Second

Value based:

It is a value based structure. We can’t store any class objects in this container. It is not a reference based data type. If you assign one container in another container, the container will be copied not linked by reference. For example:

int         i;

container   c = ['First'], d;   

c += d;

d += ['Second'];

for(i = 1; i <= conLen(c); i++)

{

    info(strFmt('%1', conPeek(c, i)));

}

Result:

First

When we use container

As per the above code, we add d container in c and adding “Second” string value in the d container after adding. But “Second” value is not added in the c container. So, if you pass container as argument to the method, it creates new container. So, performance will be slow.

If you want to handle different data types, container is the good choice. But, if you add repeated value like list in the container, it is not a good choice, because it will affect performance.

Containers are immutable

Immutable means once the variable is declaration, we can’t change the size. Here container is an immutable object. When we add, delete and update the container, new container will create.

The following statements all create a new container.

myContainer = [1]; // new container created for myContainer

myContainer += [2]; // new new container created for myContainer

myContainer4 = myContainer5; // new container created for myContainer4

Insert performance:

+= is faster than conIns function. We can use conIns when you want to insert the element in the particular index.