Given the data illustrated above, if you build the locator where you map Building to the Building Unit locator role field and Unit to the Unit locator role field you would be able to search for the following with the best results returned when an indicator is included, otherwise, the address is matched to the record in the data that returns the highest score:
- 345 W Some Bl #A > 345 W Some Bl, Building A = Match_addr
- 345 W Some Bl #1 > 345 W Some Blvd, #1 = Match_addr
- 345 W Some Bl #A1 > 345 W Some Bl, #1, Building A = Match_addr
- 345 W Some Bl, A > 345 W Some Bl, Building A = Match_addr
- 345 W Some Bl,1 > 345 W Some Blvd, #1 = Match_addr
- 345 W Some Bl, A1 > 345 W Some Bl, #1, Building A = Match_addr
If you build the locator where you map the BuildingUnit field to the Unit locator role field you will be required to enter the subunit value with a unit indicator before the value in order to get a match. If you dropped '#' from the value in the BuildingUnit field, then mapped it to the Unit locator role field you would be able to search for the subunit with or without the indicator.
We've added an option to allow subaddress suggestions before the entire unit value has been entered. Typing in the unit type, such as Apt, Unit, Suite, # is also optional. The locator will need to be created in Pro 2.9 and published to ArcGIS Enterprise 10.9.1. This new option, Suggestions for partial subaddresses, is disabled by default but can be enabled, as well as configure the number of suggestions returned, in the Locator Properties Dialog. If you are part of the Early Adopter Community or have access to ArcGIS Pro 2.9 Beta1 you can test out the functionality and provide any feedback.