Since the 'Read' action for our solution can't be triggered by a callout we
will need to enlist the assistance of the Form onLoad event. You will need to
install a HTTP Debugging Proxy like Fiddler
to get build this solution.
We will write some JavaScript to call the CRM web services on the Form onLoad
event. My colleague Arash has a
good post
on his blog on how to do this. The tricky part is building the SOAP message
and that is where Fiddler comes in
handy.
- Create a basic Console app to call the CRM Web Service and add a record
to the log entity.
- Capture that traffic using Fiddler
and inspect the SOAP packet.
- Throw away the Console app.
- Build up your JavaScript as Arash
describes.
- Add your script to the onLoad Events of the entities which you wish to
monitor.
That's it!
Here is
my script which I used.
Next: In Part 6 we will create an installer package to deploy the
application.
This posting is provided "AS IS" with no warranties, and confers no rights.
Tags: microsoft crm dynamics crm microsoft crm