Andreas Wijaya's Blog

There are two ways of getting the related entity details in many to many relationship in CRM 4.0 One way is to use RetrieveMultipleRequest function from the SDK: For example, if we have a Loan custom entity and we want to return sets of borrowers (contacts): --- Second way is to use Fetch function to return the XML of the related entities: James Downey created a nice little program FetchXMLBuilder to help you build the fetch query. --- Just for completion, below is the CRMServiceWrapper constructor that I use: Hope this helps ^_^

New Song that I created to share my Valentine Day =)

This concept tends to confuse people often - and I was no exception. I came across this problem when trying to create custom auto-numbering for one of my projects. Creating auto-number for Opportunity is easy. This is because the user creates opportunity straight from the home screen - thus the plugin runs on parent pipeline. However, it's a different story if you are dealing with Quote entity. Quote can be created in 2 ways, through the home screen OR the opportunity screen. If you create it from the latter, it will run on the child pipeline and you will find that your plugin will not work. Registering it as a child pipeline is easy, but CRM makes it harder since you can't use ICRMService. Instead, you have to create CRMService manually by using this piece of code: Not only that, with the child plugin you can't use Query expression to fetch other entities in your code unless you register it as ASYNCHRONOUS plugin. Mark Kovalcson in his blog found out that: A C...

Useful extension methods for Dynamics CRM 4.0 : My ex-colleague wrote this I believe - visit his blog for more detail: http://loosechainsaw.com CRM Service Dynamic Entity

Happy New Year Everyone ! This is my first new song in the new year ^_^ For you who don't know, my youtube channel is http://www.youtube.com/nevrene All the best and hope you can achieve your dream in 2011!

Christmas is coming everyone!! Merry Christmas ^_^

Recently I was tasked to migrate the old Asset data on Access db to SharePoint 2007. It's not difficult using 'Export to Sharepoint List' command and modified certain things such as creating new asset content type, site columns etc. I can view the list and the items. Great. but there is no print button! In Access db, they were using Access form to print the asset item. In SharePoint 2007, turns out that I have to do a bit of development to do just that. I found the nice blog on how to do this. However, I don't want to spend ridiculous amount of time playing with HTML markup to get the design I want. It is error-prone as well in terms of printing etc. Therefore, I decided to try using Reporting Service reportviewer control on the page that will render the layout. The list item details will be passed as parameters :) Cool! If you search google, you would find many articles about passing the parameters in the URL. this is not good since you will get ugly url and i...