{"id":14269,"date":"2007-02-19T12:02:00","date_gmt":"2007-02-19T12:02:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/crm\/2007\/02\/19\/another-view-of-crm-data\/"},"modified":"2023-05-31T15:32:20","modified_gmt":"2023-05-31T22:32:20","slug":"another-view-of-crm-data","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/dynamics-365\/blog\/no-audience\/2007\/02\/19\/another-view-of-crm-data\/","title":{"rendered":"Another View of CRM Data"},"content":{"rendered":"

[Code examples are on the CRM Sandbox in the downloads section<\/A>.]<\/P>
\n

MS Dynamics CRM<\/A> shipped with grid view and form view for displaying data such as account or contact information. However, that does not mean it is the only way to present CRM data. This article will show a way to represent CRM accounts on a map.
\n

\"account
Populating account’s coordinate.<\/B><\/P>
\n

Before we can show the account on the map, we first need to populate account’s location into CRM. Most account\/contact already contains shipping or billing address. However, they are not in the format that is easy to map or locate. Out of the box, account already contains ‘latitude’ and ‘longitude’ attributes that we can use but they are not automatically populated by CRM. <\/P>
\n

So we need to convert the human readable street address into latitude and longitude coordinate. This process is called geocoding. For existing CRM deployment where accounts and contacts are created without latitude and longitude, we need to mass-populate them using web service information in the CRM SDK. The are several providers that offer geocoding service such as:<\/P>
\n