$ 51.68
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) |
| Lines of code | 725 |
| Technical Name |
dom_map_view |
| License | OPL-1 |
| Website | https://demo18.domiup.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) |
| Lines of code | 725 |
| Technical Name |
dom_map_view |
| License | OPL-1 |
| Website | https://demo18.domiup.com |
Map View for Community Edition
This module adds a Community map view for Odoo with a custom view type named dom_map. It is designed as an open-source alternative to the Enterprise map view.
The first implementation is intentionally small and focused:
- It adds a backend map view type.
- It supports models linked to a partner or direct partner records.
- It reads latitude and longitude from the target partner data.
- It opens the target record from the popup.
The module ships with a sample integration on Contacts so the view can be tested immediately after installation.
Live preview is always available for you to have a look.
Using these login accounts to experience the features
| Login | Password | Role |
|---|---|---|
| demo | demo | Manager |
Usage
- Install the module dom_map_view.
- Open Contacts.
- Switch to the Map view added by this module.
- Open a contact record if you need to review or update its address and coordinates.
Only records with valid coordinates are shown on the map.
Having contact_address alone is not enough to place a marker. The map view needs numeric latitude and longitude values.
For res.partner, the view uses these fields:
- partner_latitude
- partner_longitude
- contact_address
If your contacts do not have partner_latitude and partner_longitude yet, the map will stay empty even when the address is filled in. In that case you need a separate geocoding step, either manually filling coordinates or using an optional geolocation integration.
If you install dom_map_view_geolocalize, the map view adds a Refresh button. That companion module relies on base_geolocalize to convert the visible partner addresses into coordinates and then reloads the map.
To add the map to another model, create a dom_map view and point partner_field to the partner relation used by that model.
Example:
<record id="my_model_view_dom_map" model="ir.ui.view">
<field name="name">my.model.view.dom.map</field>
<field name="model">my.model</field>
<field name="type">dom_map</field>
<field name="arch" type="xml">
<dom_map partner_field="partner_id" panel_title="My Records" default_order="id desc">
<field name="display_name" string="Name"/>
<field name="state" string="State"/>
</dom_map>
</field>
</record>
If your model stores coordinates directly on itself, set partner_field="id" and expose the latitude and longitude fields through lat_field and lng_field.
If you set default_order, use stored fields only, for example name, id, or create_date. Do not use non-stored fields such as display_name.
You can also define an initial fallback focus for the map when no markers are available yet.
Supported semantic scopes:
- focus_scope="country"
- focus_scope="state"
- focus_scope="city"
- focus_scope="street"
Optional related attributes:
- focus_source="user"
- focus_source="company"
- default_zoom="..."
This fallback focus requires dom_map_view_geolocalize, because it uses the configured geocoding provider to resolve the selected area.
Explore our Map View related modules on the Odoo App Store
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module