Set latitude and longitude
Store map coordinates for marker and map views. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Property Operations → Properties → New/Edit → Map
Before you start
- Use an account with real_property: Create or Edit and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What you’ll accomplish
Store map coordinates for marker and map views. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Property Operations → Properties → New/Edit → Map.
- Go to the exact setting, option or record named in this guide.
- Enter or select the required value; leave unrelated options unchanged.
- Save the form and wait for the success response.
- Reload the page or open a controlled record to confirm the stored value is being used.
Fields and options to review
Exact actionSet latitude and longitude
Exact navigationAdmin Area → Property Operations → Properties → New/Edit → Map
Module version1.0.0
Access rulereal_property: Create or Edit
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Rules the system enforces
- Coordinates require a working Google Maps key/loaded map; verify marker placement.
How to confirm it worked
- The supported set latitude and longitude flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.