How to know element part of which Layer and Model

How to know element part of which Layer and Model

 

Set below mentioned config: Tools > Options > Development

 

 

You will able view layer and Model on element like shown below

 

Happy Learning :)

 

 

 

 

 

Content of Model

Commands from AXUtil using command prompt:

List the elements of a model (AXUtil)

In command prompt under %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities

 

Use command:
axutil view /model:<modelname>

e.g.  axutil view /model:"ISV Model"

For finding all the element in model use /verbose in command.
e.g. axutil view /model:"ISV Model" /verbose

Deleting Model
axutil delete /model:"Model Name"
Note: Restarting AOS is required.

Validate that a model file contains data (AXUtil)

 axutil exists /model:<modelname>

Commands from Windows PowerShell

Navigation for PowerShell 

Start > All Programs > Administrative Tools> Microsoft Dynamics AX Management Shell

 

List the elements of a model:

(Get-AXModel -Model <Modelname>).Elements | Out-String

Validate that a model file contains data:

Test-AXModelData –Model <ModelName> -Verbose

 

Detail Reading @ http://technet.microsoft.com/en-us/library/hh433532.aspx

 

Happy Reading :)

Error : Cannot copy table SQLDICTIONARY from source environment to table

Error : Cannot copy table SQLDICTIONARY from source environment to table.

AX 2009 to AX 2012 Data Upgrade Check List.. We may encounter "Cannot copy table SQLDictionary error when Connecting to Source Database during upgrade" on Data Upgrade from AX 2009 to 2012. As you are proceeding through the Microsoft Dynamics AX 2012 Data Upgrade checklist, if the configuration options have not been setup properly, users can receive the following error when using the Connect to source database window from the Data Upgrade Checklist: Error Message: Cannot copy table SQLDICTIONARY from source environment to table Error Message: Exception has been thrown by the target of an invocation.Specified argument was out of the range of valid values. Parameter name: DestinationTableName This error is caused if the Keep update objects 6.0 configuration key found under the Administration tree node has not been marked. Setting configuration options during the Data Upgrade Checklist varies slightly depending on which version of Dynamics AX 2012 is installed. If using Dynamics AX 2012 CU-3 or higher, or with the Dynamics AX 2012 Feature Pack installed, the License configuration window can be opened from the Upgrade preparation part of the Data Upgrade Checklist under the option Configure application functionality. If using a version of Dynamics AX 2012 RTM prior to CU-3, then the user will have to do the following steps: Press Ctrl-D while looking at the checklist to go into a developer workspace Open the AOT and navigate to to Menus – SystemAdministration – Setup – Licensing Right click on the Licensing menu option and choose Open Once the License configuration window is open, it is important to expand the Administration tree node and make sure that the Keep update objects 6.0 and Keep update objects 5.0 options are marked. The entire tree should be examined and the configuration options for the other modules should be setup the way that your previous source version of Dynamics AX was setup. Some of the key options may have changed or possibly removed, so set up your options based on how they were in the previous version and how you intend to use the functionality in the new version. Failing to mark a configuration option could lead to data from the source environment to not be copied into Dynamics AX 2012.

CLRObject could not be created error While Clicking Tools --> Option

CLRObject could not be created error While Clicking Tools --> Option

 

This could be due to hot swapping feature in AX 2012.

 

Uncheck "Enable the hot-swapping of assemblies for each development session" option mentioned  in AX Server Configuartion Utility as shown below.

 

What is Hot Swapping:

 

In your development environment, you can use the hot-swap feature of the Application Object Server (AOS) to use updated assembly DLL files without having to repeatedly stop and restart the AOS. Restarting the AOS terminates the connections from other developer clients, which can be an inconvenience.

Scenario with Hot-Swapping Off

The hot-swap configuration value is set to off when Microsoft Dynamics AX is installed. Under this default, one application domain is created when the AOS starts. No additional domains will be created. All .NET Framework assemblies that are loaded into the AOS share the single domain. Also, the single domain is shared by all client connections.
To test the updated assembly, you must restart the AOS. Then connect an AX32.exe client to the AOS, and run the tests. Having to restart the AOS after every compilation is inconvenient. The inconvenience is increased if other developers are sharing the same AOS, because their connections are broken with each restart. Their connections can be from an AX32.exe client, and from Visual Studio.
It is not necessary to stop and restart the AOS when you need the AOS to load a new assembly that it has not loaded before.

Scenario with Hot-Swapping On

When the hot-swap configuration value is on, each new client connection to the AOS is assigned to a new application domain that is dedicated to that connection. Each connection has its own application domain. The creation of new application domains does not affect other connections.
Each new application domain is populated with the versions of assembly DLLs that are available to the AOS when the DLLs are loaded into the new domain. In any given application domain, no updates can be made to any assembly DLL that is already loaded into the domain.
In Visual Studio, after you modify your C# code and again compile the assembly DLL, you only need to start a new AX32.exe client to gain access to the updated assembly for testing.


Learn more about Hot-swapping @  http://msdn.microsoft.com/en-us/library/hh538487.aspx

Failed to create a session; confirm that the user has the proper privileges to log on to Microsoft Dynamics.

Failed to create a session; confirm that the user has the proper privileges to log on to Microsoft Dynamics.

 

When I performed DB Sync. got the above mentioned error.

Uncheck "Execute Business Operation in CIL" helped me. It prevent code to get converted in CIL for better execution and code execute in older way as it was in AX 2009.
Navigation : Tools --> Options

 

 

Happy Learning.

 

 

Important Links

Please find few important links, which really can help in moving AX 2009 to AX 2012:

Upgrade to Microsoft Dynamics AX 2012 [AX 2012]
http://technet.microsoft.com/en-us/library/dd362002

Issues with AX 2012 with TFS
https://community.dynamics.com/ax/b/daxmusings/archive/2011/11/17/ax-2012-and-tfs.aspx

Models, Layers, and the Model Store [AX 2012]
http://technet.microsoft.com/en-us/library/hh335184.aspx

Data Upgrade Scripts for Microsoft Dynamics AX 2012
http://msdn.microsoft.com/en-us/library/30eee91e-6b1d-44ce-8cac-b6a6e89bc954(v=ax.60).aspx

Install the Microsoft Dynamics AX databases [AX 2012]
http://technet.microsoft.com/en-us/library/ee355075.aspx

How to: Create a Repository [AX 2012]
http://msdn.microsoft.com/en-us/library/aa851066.aspx

How to: Add Filter Controls to a Simple List Form [AX 2012]
http://msdn.microsoft.com/EN-US/library/hh745335.aspx

What's New: Visual Studio Tools for Developers in Microsoft Dynamics AX 2012 [AX 2012]
http://msdn.microsoft.com/en-us/library/gg863931.aspx#BKMKMgdCodeBusLogic

Database Upgrade from Older version to AX 2012
http://blogs.msdn.com/b/axsupport/archive/2011/12/11/planning-your-data-upgrade-to-microsoft-dynamics-ax-2012.aspx

AX & TFS FAQ
https://community.dynamics.com/ax/b/daxmusings/archive/2011/06/29/ax-amp-tfs-faq.aspx
http://daxmusings.codecrib.com/2011/06/ax-tfs-faq.html

TFS workspaces in AX2012
http://dev.goshoom.net/en/2012/07/tfs-workspaces-in-ax2012/

Shared vs. isolated Dynamics AX environments
http://dev.goshoom.net/en/2012/06/shared-vs-isolated-ax/

Introduction

I am working on what it takes to move one enterprise application from Ax 2009 to AX 2012, and would like to post my experience in this Blog. Just daily watch this space for more activity.
Please share your experiences with me for make AX community learn better.