magicKey doesn't work with custom composite locator

[LeonZhong]

Hi,

I published a composite locator from arcGIS Pro to ArcGIS server. Everything looks fine except magicKey.

For example, first call sugguestion:

Then call findCandidate:

I just copy the text from suggestion to SingleLine and also copy magicKey as well.

Anybody has same issue before?

Thank you,

Leon Zhong

[BradNiemand]

Michael,

Can you explain the exact workflow that you do with potentially an example?  I am still unsure what the exact issue is that you are having.  In general though, this patch is specific to locators created with the Create Locator tool in Pro so it will not address issues related composite locator that contain locators created with the classic tool, Create Address Locator.

Are you entering an address, getting a suggestion, passing in that suggestion text with magicKey to findAddressCandidates and then not getting a result?  If so, does the address actually exist in the data?  The classic locators had a limitation that would not verify the house number for performance reasons so in some cases you would get back suggestions for addresses that didn't exist in the data.  In that case if a suggestion with an incorrect house number was sent to the locator, you would get no match because it doesn't exist.

The limitation is resolved with locators created with the Create Locator tool.

Brad

[MichaelVolz]

A co-worker worked with ESRI tech support where they watched network traffic with F12 developer tools to see the difference between suggestions generated with the composite geocode service (list of results by user typing in address without hitting enter) and results generated by the composite geocode service (list of results by user typing in address then hitting enter).  The magicKey was different for the suggestions as opposed to actual results.  The ESRI tech support specialist then copied the URL of the suggestion and replaced the magicKey with the same address result magicKey and a result was returned instead of no valid results.

The ESRI tech support analyst then provided the link to the ArcGIS Server 10.7.1 General Geocoding Patch, but at this point I'm not sure if the analyst was providing this as a solution or a possible solution as I am working with the Create Address Locator tool and not the Create Locator tool that is only available in Pro.

[BradNiemand]

Michael,

The goal of this patch was to address issues with composite locators that contain locators created with the Create Locator tool.  There may be some additional benefits that would be seen with composites that contain classics locators as well but that was not a focus of the testing for this patch.  I would say it wouldn't hurt to give it a try but I can't guarantee that it will help.

If the patch does not help, I would suggest that you reopen or follow up with the tech support analyst and have them contact me about this.  They might be able to walk me through the issue or provide me with data to reproduce it on my side so I have more information for you because I am still not sure I understand the issue completely.

All that being said, I am not sure if you have looked into the new locators but I would suggest that you do because they have a lot of benefits over the classic locators (size, performance, quality, new features, etc....).  The locators can be used in Pro 2.3 or newer or published to ArcGIS Enterprise 10.6.1 or newer (with the patch(s)) and used from other Esri clients, including ArcMap.

Brad