phone number to map automatically

there is not a simple way to know from which kind of view the query comes.

if "automatic number field suggesting" is going to be implemented then there comes the need
to implement a generic way to handle this for all kind of situations.

if so there's the possibility that a wrong field is automatically selected and i think it's better to prevent this
(than to risk to assign a wrong field automatically)

i mark this as won't fix by now. if there'll be a common need for this feature then i'll look for a redesign
(maybe adding a view option to assign the number field directly when building the view ?)