Last year, I wrote about the challenge of cross-domain calls from JavaScript with CRM 2011. The issue was related to fact that from a security perspective, you could not have JavaScript functions executing on a CRM form event or when a ribbon button is clicked calling web services outside of the CRM domain. I proposed a few workarounds here but the bottom line is that in all cases, there was some sort of a negative impact in each solution. With CRM 2013, actions processes are a great way to get around the browsers’ cross domain restriction.
In this article, I am providing an example of how actions can be used to make a request to a web service outside of the CRM domain from a record’s form event.
Scenario
When users call an incident management center, the agents need to capture the temperature at the time of the incident in…
View original post 425 more words
Share this:
