Rahul Sharma


{Rahul Sharma}

Blog
This blog is for all those techies out there who are really passionate about Microsoft Dynamics AX, Microsoft Dynamics CRM, .Net, SharePoint, SSRS, SQL Server, SSIS and related technologies. Join this blog on facebook {Rahul Sharma}, to start a discussion !!!

Index | MS Dynamics AX | MS Dynamics CRM
View blog as >> Magazine | Sidebar | Flipcard | Mosaic | Snapshot | Timeslide

Dynamics AX 2012 R3 Mobile Apps Configuration Using Self-Signed Certificate

In the last post we deployed Dynamics AX 2012 R2 DEMO instance on Microsoft Azure. If you don’t have it yet, I will recommend going back to the post “Use Lifecycle Services to deploy Dynamics AX on Azure” and complete the deployment.

In this post we are going to setup Dynamics AX Azure instance for Dynamics Mobile Apps using a Self-Signed Certificate. This is only for development / demo environments. In production, we will be using certificate from the Public CA like godaddy etc. Also remember we only have one DEMO VM with all AX components installed on it.

Use Lifecycle Services to deploy Dynamics AX on Azure

Let's deploy Dynamics AX 2012 R3 on Microsoft Azure in less than 60 minutes.

Step 1)
Login to Lifecycle Services using your CustomerSource or PartnerSource account.

Step 2) Create LCS Project
A project is an umbrella to manage AX implementation. Customers and Partners can invite each other to participant in the implementation process.

Publish Dynamics AX client as RemoteApp on Remote Desktop Services

It is a normal practice to give users access to Dynamics AX either by installing the AX client on their computer or providing Remote Desktop so that they can connect to the computer which already has AX client installed.

We can provide more robust and rich experience to users that will give them the feel of a local application and ease of remote desktop by publishing AX client to RemoteApp server. It is same as using remote desktop services to connect to a desktop but instead of the desktop user will connect to the AX client only, giving him the experience as if it is locally installed on the user's machine.

Once AX client is published to RemoteApp server, user can access the client using the RDP connection via Remote Desktop Web Access portal or via a MSI file to install an AX icon on the desktop that will have a connection to access RemoteApp.

Dynamics AX 2012 & SQL Reporting Services 2012 Reporting Extensions Error

You might come across to this error when installing Dynamics AX 2012 Reporting Services extensions on a fresh install where you never had SQL Server 2012 installed before.

We prepared a separate server for SQL Server Reporting Services 2012. We used a slipstreamed Dynamics AX 2012 Feature Pack setup to include the AX CU3 update and SQL Server 2012 Compatibility Hotfix KB2680186 . We went ahead to install Dynamics AX 2012 Reporting Services extensions on this server but installer did not finish and complained about few missing .NET assemblies.

An error occurred during setup of Reporting Services extensions.
Reason: Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=10.0.0.0 ...

Or

An error occurred during setup of Reporting Services extensions.
Reason: Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=10.0.0.0 ...


This error can be easily resolved by installing Microsoft® System CLR Types for SQL Server® 2008 R2
X86 Package(SQLSysClrTypes.msi)
X64 Package (SQLSysClrTypes.msi)
IA64 Package(SQLSysClrTypes.msi)

Discuss this on facebook.

Join me on facebook and feel free to post your comments / feedback / queries.

Claims-Based Flexible Authentication in Dynamics AX 2012

Dynamics AX 2012 provides a new way to authenticate users in AX, called claims-based / flexible authentication. In this approach, you don't have to create users in Active Directory first to give them access to use AX Enterprise Portal / AIF. And this is really a very nice and a way to go approach for giving AX access to external users who are not part of the organization's Active Directory structure. For example; now you are no longer required to create vendors and customers in Active Directory to have them access vendor self-service portal or customer self-service portal respectively.

Dynamics AX for Retail POS Development - Code Samples

In this post, I am going to share some .Net POS code samples to get you going with Retail POS coding.

Dynamics AX for Retail POS Development

This article is a kick start for customizing AX for Retail POS. We will see how we can modify or create new touch screen forms, operations & tables in POS system. At the end, you will also see some code samples that will also give you the feeling of how code looks in POS.

Upload of Fetch-Xml report fails with VB Code - Dynamics CRM

This is a quick reference to keep things in mind while writing VB code on Fetch-Xml based SSRS reports. You need to avoid using below functions otherwise you wont be able to upload your reports to Dynamics CRM Online.

Add new Context Menu in AOT to Browse Table with Grid Toolbar - Dynamics AX

In this article we will see how we can extend Dynamics AX table browser to have standard grid toolbar like all other Dynamics AX forms. We will also create a new context menu in AOT > Data dictionary > Table > Add-Ins, called "Table browser - Advance", which will show us our advanced table browser and the default Table browser context menu command will show standard table browser as usual.

Change File Ownership through X++ in Dynamics AX

This article shows a little trick that might be needed for testing AX AIF file adapter based integration. We all know that how frustrating it can be to setup input file ownership to current AX user while testing otherwise AX will complain about it.

Here is a small static function with filepath as a parameter. This function will set current AX user as the owner of the input file. This function can be called right before the call to fileSystem.ReadFile(filePath) in \Classes\AifFileSystemReceiveAdapter\readFile.