AnsweredAssumed Answered

Geocoder dijit in JS API v3.3 bug? "SingleKey" vs "singleLine" search parameter name.

Question asked by jay.gregory on Jan 11, 2013
Latest reply on Apr 12, 2013 by DSwingley-esristaff
I instantiated a geocoder in my app using the new geocoder dijit (I am very excited about this).  However, it doesn't work using my custom geocoder (ArcGIS for Server 10.1 SP1).

//geocoder digit   var geocodersArray = [{url: "", name:"Landing Facility Geocoder"}];   var geocoder = new esri.dijit.Geocoder({           map: map,           autoComplete: true,     maxLocations:10,      geocoders: geocodersArray,     geocoderMenu: false,     arcgisGeocoder: false         },"search");         geocoder.startup();       }

As far as I can tell (from Firebug) the request the geocoder dijit sends is:
" Angeles International Airport&f=json&outSR=%7B%22wkid%22%3A102100%7D" plus a callback. 
No results are returned. 
If I run the same query directly from the REST endpoint on my server, I get
" Angeles International Airport&Single+Line+Input=&outFields=&outSR=&searchExtent=&f=pjson", and results are returned. 

The difference seems to be that the geocoder dijit is using "singleLine" as the search parameter name, while ArcGIS for Server is using "SingleKey" or "Single Line Input" for the search parameter name.  I tried replacing "SingleKey" with "singleLine" in my server query, and, as expected, no results are returned.  So is this a bug in the geocoder dijit or am I missing something?

Thanks, Jay