It is possible as discussed elsewhere in this blog to share information / tables across companies, this is done using an AOT entity called a TableCollection.
I had some trouble sharing some specific tables as you can see from the error report I made and I had to resolve the issue by manually changing the XPO file and importing it as it was not legal to do it in Axapta itself.
Here is the error report or an extract of it.
I have a client who wishes to share the LedgerTrans Table and therefore also the LedgerBalancesTrans and LedgerBalancesDimTrans Tables as logical extensions to this.
In order to ameliorate performance MS has introduced the views LedgerBalances and LedgerBalancesDim.
It is not possible to add a View to a table collection in the AOT, as a consequence the view tries to view transactions in the curext() company and therefore does not find any transactions.
I have resolved the issue by manually in an XPO file adding the LedgerBalances and LedgerBalancesDim Views in the collection, this has the desired effect however it would be nice if we could do so in a "Legal" manner.
The answer from support is that it is possible to type the view in manually and fortunately it is ;-), I only hope that this will remain true.
Anyhow the upshot is that if you ever need this then you now know it is possible manually without using the drag and drop.
/Sven
Showing posts with label Virtual Cpys. Show all posts
Showing posts with label Virtual Cpys. Show all posts
Monday, 6 November 2006
Sunday, 5 November 2006
Sharing and Virtual Companies in Dynamics Ax
An often misunderstood part of Dynamics is it's ability to share information in between companies.
Why do I say that it is often misunderstood ?
Because it is presented as a solution to the much more complicated arena of multicompany / departments sharing in modern companies.
In Dynamics there is no native mechanism that enables the control / setup of such entities in the product.
You have to work and develop based on the needs of the customer the controls and mechanisms that you see are needed by the customer.
The Virtual companies are only a mechanism to start this process, they allow you to dictate that information contained in certain tables as a whole are availeable to both companies.
In every table in Dynamics Ax there is a column called DataAreaId which contains the company that the entry belongs to, and what you do when creating a virtual company is just that you replace the information contained in the row with the virtual company id and when you add companies to the virtual company you change the way they search that / those tables. Instead of using their own company id to search they use the virtual company id to search.
This basically allows one to share information / maintain / create information in a shared manner. Of course it does not really enable one to create a business unit within an organisation spanning several companies in several countries, in order to do that some work is required :-).
Later I will detail some quick solutions to some quirks in doing such sharing and illustrate by examples from implementation projects what can be done in this arena as well as some ideas of what would be nice as additions in order to support this functionality better.
/Sven
Why do I say that it is often misunderstood ?
Because it is presented as a solution to the much more complicated arena of multicompany / departments sharing in modern companies.
In Dynamics there is no native mechanism that enables the control / setup of such entities in the product.
You have to work and develop based on the needs of the customer the controls and mechanisms that you see are needed by the customer.
The Virtual companies are only a mechanism to start this process, they allow you to dictate that information contained in certain tables as a whole are availeable to both companies.
In every table in Dynamics Ax there is a column called DataAreaId which contains the company that the entry belongs to, and what you do when creating a virtual company is just that you replace the information contained in the row with the virtual company id and when you add companies to the virtual company you change the way they search that / those tables. Instead of using their own company id to search they use the virtual company id to search.
This basically allows one to share information / maintain / create information in a shared manner. Of course it does not really enable one to create a business unit within an organisation spanning several companies in several countries, in order to do that some work is required :-).
Later I will detail some quick solutions to some quirks in doing such sharing and illustrate by examples from implementation projects what can be done in this arena as well as some ideas of what would be nice as additions in order to support this functionality better.
/Sven
Subscribe to:
Posts (Atom)