Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Info

This guide has been reviewed against our global client base and classed as relevant to the following regions: UK, APAC, UAE

You may find that you have an applicant that won't match to a property, or vice versa. There is always a good reason as to why this is happening.

This article explains the steps to work through to resolve a matching issue. 


1. Remove match filters

  • From the property/applicant record, click Match

  • From the match filter screen, remove each filter tick box, one by one, leaving each box un-ticked after every match attempt

    This allows you to see which filter is preventing the records from matching, as you un-tick each one

  • e.g. first remove Acreage filter then click Accept to run the match
    • Check for the required record
    • If not shown, return to the match filter screen
    • Remove the next filter, and repeat



2. Example

  • The Acreage filter was removed first, but clicking Accept to run the match did not show the expected applicant in the match result

  • The Location filter was then removed and Accept clicked to run the match

    The expected applicant appeared in the match results

  • This check then pinpoints that the property/applicant Location is affecting the match


Note

If the match only appears after you have removed all filters, this pinpoints that it is one/more of the following that is affecting the match:

  • property Department
  • property Available setting
  • property Price/Rent

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a45
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "match" and type = "page" and space = "RW"
labelsMatching match matches

Page Properties
hiddentrue


Related issues