Enable Geocode capabilities by default on geocoding service

[ChelseaRozek]

I was able to publish and overwrite geocoding services fine with ArcGIS Pro 3.5.

As of Pro 3.6, when publishing to server 11.5+, Geocode is not appearing as an allowed operation.

Even with everything checked, I have to go into Server Manager after publishing and manually check Geocode on under Operations Allowed so that my applications don't break. Otherwise, if you try to use Find Address Candidates on the REST endpoint, it just says "requested operation is not supported by this service".

I put a support ticket in about this, but I was told it was "as designed." That doesn't seem good, though, as it breaks the ability to use the geocoding service in my applications to search for addresses.

[Robert_LeClair]

In reviewing the case, the analyst did create BUG-000181366 - "Geocode capabilities are not enabled by default when publishing from ArcGIS Pro 3.6 to ArcGIS Enterprise" and it was marked "as designed" as you mentioned.

The explanation I see is:
The behavior is expected and is as designed. When publishing a locator from ArcGIS Pro 3.6 to ArcGIS Enterprise 11.5 or later, the Geocode capability will not appear as an allowed operation. The Capabilities section on the Configuration tab is context sensitive and dynamically updates the list of operations based on the server the locator is published to. The default capabilities in ArcGIS Pro 3.6 when publishing to Windows or Linux ArcGIS Enterprise 11.5 or later are:
- Find Address Candidates, to find a list of addresses or places.
- Geocode Addresses, to geocode a table or batch of addresses or places.
- Reverse Geocode, to return the nearest address for a geographic location.
- Suggest, to generate autocomplete suggestions for partial input strings.

As I work in Esri Training Services, I have zero sway on the development cycles but it's a good idea to consider certainly.

[ShanaBritt]

@ChelseaRozek The Geocode capability that you see when publishing from ArcGIS Pro 3.5 or 3.6 to ArcGIS Enterprise 11.4 or earlier means that the geocode service will support geosearch (FindAddressCandidates operation) and batch geocoding (GeocodeAddresses operation). A change was made to allow users to publish a geocode service that only supported geosearch (FindAddressCandidates capability) or to only support GeocodeAddresses operations. If both Geocode Addresses and Find Address Candidates are selected, then the service supports both by default. This change can also be seen for utility services in Online and Enterprise portals. If you published from 3.6 to 11.5 or later with the new default capabilities and went to ArcGIS Server Manager and checked the Geocode capability you would be duplicating capabilities.

Can you provide more details about your application that is broken unless you check the Geocode capability in ArcGIS Server Manager? What is the application based on? What does the application do? Is the app based on an esri solution or app?

[ChelseaRozek]

Hi @ShanaBritt , thanks for responding. I did have everything checked on when publishing, but FindAddressCandidates fails even on the REST endpoint until I check on the Geocode operations allowed that I circled in red. It broke in our main parcel viewer application that we built with VertiGIS Studio Web. All it has me do is enter the .../GeocodeServer service URL for the search box to work. It is a publicly available geocoding service, so no security elements to worry about. I'll send you a message with the exact URLs so you can see.