| Info |
|---|
This guide has been reviewed against our global client base and classed as relevant to all regions |
You may find that you have an applicant that won't match to a property, or vice versa - 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
|
...
|  Image Added |
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
|
...
|  Image Added Image Added |
...
| Tip |
|---|
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: |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a45 |
|---|
| sort | modified |
|---|
| showSpace | false |
|---|
|
...
| | reverse | true |
|---|
| type | page |
|---|
| cql | label = "match" and type = "page" and space = "RW" |
|---|
| labels | Matching match matches |
|---|
|
| Excerpt |
|---|
|
Steps to work through if you find you have an applicant that won't match to a property, or vice versa |
