Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Fixing Longitude and Latitude Attributes

0 views
Skip to first unread message

Ed

unread,
Feb 17, 2006, 7:48:23 AM2/17/06
to
Greetings.

The default attributes for the Address Longitude and Latitude fields are
bad. While the TYPE is float, the precision is only 2 decimals and the min
and max values make no sense. (0.00 - 1,000,000,000.00) For example, 1
Microsoft Way in Redmond should be Lat: 47.64490 Long:-122.13023. As seen
here:

http://terraserver.microsoft.com/image.aspx?t=4&s=8&Lon=-122.13021640&Lat=47.64468123&Alon=-122.13021640&Alat=47.64468123&w=1&opt=0&addr=1+Microsoft+Way%2c+Redmond%2c+WA+98052&qs=1+Microsoft+Way%7cRedmond%7cWA%7c

I have gone in and adjusted the Minimum & Maximum values, as well as the
Precision. I've published the Address table, but the changes don't reflect
on the primary Account screen. (I've added those fields to the general tab)
If I go in and create another address in the "More Addresses" area, it DOES
respect the new configuration. I've also tried to publish the Account table,
in case there's some relationship that also needs to be updated.

Any suggestions?

Also, is there a way to increase the precision of float fields? It's a
drop-down and the most I can select is 5 and I'd rather a more exact LONG/LAT
in the system.

TIA!

--Ed

Matt Parks

unread,
Feb 17, 2006, 2:57:54 PM2/17/06
to
Ed,

This will be unsupported, so proceed at your own risk...(and make sure you
have backups or both CRM & Metabase DBs)

This information is stored in the Metabase DB in the Attributes table. The
problem with changes to Addresses not being reflected in Account & Contact
is a known issue. Address fields are basically added to Account & Contact
as virtual fields that map to the underlying address fields. But, in the
metabase, they have distinct rows in the Attribute table. So, you should be
able to update the Attribute records for the Addres1 & address2 long & lat
fields for the Account & Contact in this table. I'd bring up the records
for those & the address table cols and see which fields to change to reflect
this change.

--

Matt Parks
MVP - Microsoft CRM


"Ed" <E...@discussions.microsoft.com> wrote in message
news:1A471E2E-7733-4D67...@microsoft.com...

RJ Samp

unread,
Feb 18, 2006, 6:00:25 PM2/18/06
to
When will this bug be fixed?

RJ Samp


"Matt Parks" <mattp65@Yax_RemoveDashAndX_xhoo.com> wrote in message
news:eMwQEy$MGHA...@TK2MSFTNGP10.phx.gbl...

Matt Parks

unread,
Feb 20, 2006, 3:32:11 PM2/20/06
to
Not sure. Since it is a holdover from v1.x, I wouldn't expect anything
anytime soon. Afraid they consider this "as designed".

--

Matt Parks
MVP - Microsoft CRM


"RJ Samp" <rjs...@avantesolutions.com> wrote in message
news:OKoH68NN...@TK2MSFTNGP12.phx.gbl...

0 new messages