Understand property-option detection
This guide explains that why the linked-property list may differ between installations. 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 → Licence Applications → New/Edit Application
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What you’ll accomplish
Know why the linked-property list may differ between installations. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the form.
- Check whether the expected property appears.
- If missing, verify the installed property module/table and record count.
Fields and options to review
Detected labelsproperty_name, name, address, property_address or title
Limit500 rows
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/
Rules the system enforces
- The supplied case form and model apply this behaviour.
How to confirm it worked
- Understand property-option detection completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.