Hi All,
We need to list down the tables with Module wise in Dynamics 365 for Operation.
If there is any possible way to do that??
Thanks,
Karthick.M
*This post is locked for comments
Hi All,
We need to list down the tables with Module wise in Dynamics 365 for Operation.
If there is any possible way to do that??
Thanks,
Karthick.M
*This post is locked for comments
The Application code consists of many packages including the standard ones that Microsoft shipped (ApplicationFoundation, ApplicationPlatform, ApplicationSuite, Calendar etc) and any custom packages. In individual package folder, a folder named "Descriptor" is present that holds the information of the package, the packages it references and the modes that are part of this package. The file is in XML format. Each package consists of one or more models (Model 1, Model 2...Model n). In the model folder there is a folder for each AX object type (AxClass, AxEDT, AxTable etc). The information (code etc) for individual objects is stored in a XML file.
In AX7 the application code is saved in file system in a directory and is called PackageDirectory. The location of directory (along with other settings) is saved in a web.config file. In IIS right click on the site "AOSWebApplication" and click on Explore. In the folder, find web.config, open it with notepad and search for "Aos.PackageDirectory". This will have the location of application directory. e.g. C:\Packages. This file also contains the information of the business database location.
A file based model store allows for quick search - xml allows complex searches using XPath and XQuery to find properties. There is a tool –‘ basex’ - which is a light weight xml database engine and it provides very powerful query and searching.
Download it from the site http://basex.org (mentioned by Peter Villadsen’s session at the recent tech conference. Mining the Metadata and Authoring X++ Best Practice Rules in Microsoft Dynamics AX) Create a new Database and select the Packages folder. Make sure to tick skip corrupt files because s there is 1 file it is not well formatted xml.
Thank you Martin...
It all depends on your definition of "module". It may be a model or a package. It may be a configuration key. It may be a prefix of table names. All these things can be done. But there surely can be definition of module that aren't stored in metadata and therefore can't be evaluated automatically.
André Arnaud de Cal... 291,431 Super User 2024 Season 2
Martin Dráb 230,503 Most Valuable Professional
nmaenpaa 101,156