Unable to connect to the remote server in D365

 Exception:

While exporting data from local VM of Dynamics 365 for Operations, you might get an error if the Azure storage emulator is not running.

Microsoft.WindowsAzure.Storage.StorageException: Unable to connect to the remote server —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it.

Resolution:

You can start the Azure storage emulator by following the steps below:

1. On OneBox VM, run command prompt as administrator.
2. Navigate to “C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\”
3. Run “AzureStorageEmulator.exe start”

This should resolve the issue reported above which surfaces while exporting data through data entities in Dynamics 365 for Operations.

Open table browser in IE/Chrome browser - Dynamics 365/AX7

In order to view the table data, normally from VS(visual studio) we can right click on the table and select the "Open table browser", it open up the table with data.

Other way we can view the table data in the IE/Chrome browser by using the below method:

https://<AX7 URI>/?mi=SysTableBrowser&prt=initial&cmp=<Company>&tablename=<TableName>&limitednav=true

AX7 URI : XYZ.cloudax.dynamics.com.

Company: "USMF","GBSI" or which company wanted to view the data.

TableName: Mention the AX table name i.e. like Customer/Vendors/CustGroup - which table data wanted to be viewed.

https://XYZ.cloudax.dynamics.com/?mi=SysTableBrowser&prt=initial&cmp=GBSI&tablename=VendGroup&limitednav=true

Development Basics in Dynamics AX 7

 AX7 is based on few new terminologies, which are as under:

·       Element: Element is the object in the AOT(Application Object Tree) such as tables, classes, forms etc.

·       Model: Model is defined as collection of elements that represent a distributable software solution. This included all the elements and the Metadata. Model belongs to only 1 package. You can modify elements belonging to same package where the model belongs. Model is a unit of development/customization.

·       Packages: Package is a deployable container. It contains source files (XML files), resources and DLLs. It is similar to Model store of AX 2012. You can select one or more packages and create a deployable package, which can be used to move the code from one environment to other. Packages are stored under c:\packages folder. For every model new sub folder will be created under package folder. Package is unit of deployment.

·       Project: Project is a small, manageable group of elements. If you want to customize the element, it needs to be added to the project. Project always belongs to only 1 model. We can use project files to import/export between different instances of AX. It is saved as .AXPP file. 
Solution: Solution is a virtual grouping of projects in Visual Studio. In Visual Studio you can add project from same or different models from one or more packages.

Overlaying

Overlaying means if you customize any element in upper layer, it will override its definition, in lower layer. This is what we were doing till AX2012 to customize AX. It basically allows customization of metadata and source code in a higher layer.

Extension

It refers to the concept of extending existing elements, without overriding those present in other layers. That means, elements will not be customized, instead elements will be extended. By creating extension elements, all of the customizations and code are stored in a separate assembly. It only contains the code that was added or changed in the extension file.

Before working in Visual Studio we need to do few settings which will make the development experience with AX a little smoother.

Step 1:- Go to AX 7 Options

Step 2:- Set Projects Options

Step 3:- Set Text Editor Options

Step 4:- Set Best Practice Options