Today I was working at a custom front end application for Microsoft Dynamics CRM, a project I have been blogging about before. The goal of that project is to create a client portal showing information directly from the CRM. I am going to describe to you the 3 steps you need to take to implement your own front end for Microsoft Dynamics CRM.
Last week at Liones we started a custom front-end project for Microsoft Dynamics CRM 4.0 and I am one of the developers working on the project. It is my job to write a library around the web service which MS CRM provides. The service itself is pretty easy because it contains only 7 methods:
The difficult part is to get the queries right because it is hard to determine how entities are related to each other if you don’t know the system. However I found a really useful tool to do this for me: FetchXML Wizard.
This is just a short post, next time I will tell you more about my adventures with MS CRM.
For my work at Liones I am writing a technical design for a shopping cart. The requirements are fairly basic, except for one: the shopping cart must be generic to support any payment service provider (psp) and customer relationship management (CRM) system. Also there might be several different product types in the future, like: subscriptions, downloads, pay per use, etc.. These requirements make the shop very complex and a great challenge.
I started with an investigation on the internet about this subject and I quickly found out that there aren’t much articles on this topic around, but I found a few very interesting ones though. Next I started to draw some UML diagrams; I added some best practices like the Money class.
