Versions Compared

Old Version 1

changes.mady.by.user Dave Marshall

Saved on

compared with

New Version 2

changes.mady.by.user Dave Marshall

Saved on

Key

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

You may find that you have an applicant that won't match to a property, or vice versa. There is always a good reasons as to why this is happening - This article explains the steps to resolve your matching issue. 


1. Open your Property/Applicant record.

  • Click Match (Bottom left of the record)


  • Remove each Filter 1 by 1, ensuring that you leave them un-ticked after doing so. By doing this we can determine which filter is preventing the records from matching


  • In the Example, you will notice that i have removed the Rural/Acreage/Keywords and that did not show the applicant i was expecting. However, when i removed the Location filter, my applicant was appearing in the match results


  • With this information, i know that it is the Property/Applicant location that is effecting this match


Note
titlePlease Note

If the match only appears after you have removed all filters, then you know that it is either the Department, whether the property is available or the price of the property that is effecting this match


Example:


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

Page Properties
hiddentrue


Related issues