The PX property module can return unexpected errors during property searches, saleout processing and reservation lookups. This article covers the most common causes and how to resolve them.
Property search returns no results
If a search in the PX module returns no matching records, the cause is usually an active filter, a restricted date range or an incorrectly configured REGOTYPE parameter.
Check your search filters and date range
Open the PX module and go to the relevant search screen.
Review any active filters — check that status, region and property type filters are not too restrictive.
Expand your date range to cover the full expected period.
Clear all filters and retry the search to confirm whether filters are the cause.
Check the REGOTYPE parameter
The REGOTYPE parameter controls which property types appear in search results. If it is not configured correctly for your environment, searches may return no results even when records exist.
📌Note: If you are unsure which REGOTYPE value applies to your setup, contact your system administrator or raise a support ticket before making changes.
Saleout and reservation lookup failures
If a saleout or reservation lookup fails or returns an error, the following steps help identify the cause.
Confirm the plot or unit reference is correct and exists in the system.
Check that the reservation or saleout has not already been cancelled or superseded.
Verify your user account has the required function access rights for the PX module.
If the issue persists, note the exact error message and raise a support ticket.
⚠️Important: When raising a ticket, include the plot reference, the exact error message and the steps you completed before the error occurred. This helps support investigate more quickly.
Raise a support ticket
Raise a support ticket if:
Your search returns no results after clearing all filters and checking parameter configuration.
A saleout or reservation lookup fails with an error you cannot resolve.
You see errors referencing missing or unrecognised parameters.
Include the module name, the action you were performing, the exact error message and a screenshot where possible.
