Showing posts with label address attribute. Show all posts
Showing posts with label address attribute. Show all posts

Monday, October 18, 2010

How to Show address using Bing Map in CRM 2011?

CRM 2011 provides a different feature to use java script as compared to CRM 4. In CRM 2011 you cannot write script directly in form event. Here they have provided a facility to create form library where you can write your own java script function. Only after creating a form library user will be able to call the function on form or field event.

To use the script on field or form event you will need to add a event handler, where you can specify the web resource library file and function name.

Follow the steps to create a form library file as shown below in the Screen shot.

• Click on Add button to add new form library


• You can add existing web resource or can add new web resource. Fill the details as below screen shot. To add the script click on Text Editor button and write the script.


• To use this function on Form load event you need to add event Handler and write the function as below screen shot.

• Select the library name in which you have write the script function and function name as below screen shot.

• Now save and publish the entity.

Note: if user is doing any modification on form library file then you need to go to web resource and select file and Publish it.

When you will open records, the Bing map will plot location in map.

Hope this help to understand how to use Bing map in CRM 2011.

Wednesday, January 13, 2010

Increasing the length of address1_line1 attribute does not work - FIX

We once happened to increase the length of the adress1_line1 attribute of account to 200. We had done this before with other attributes and it had worked just fine.

So we were surprised when even after publishing the account entity after make the above change, we still received an error.

To Fix this Error we had to instead increase the length of line1 attribute of the “customeraddress” entity and publish this entity.

Once the above change was published we did not receive any more errors related to street1 attribute on the account entity.