Single Line Address Field:
SingleLine (Type: esriFieldTypeString, Alias: Single Line Input, Required: false )
Candidate Fields:
Score (Type: esriFieldTypeDouble, Alias: Score)
MatchLevel (Type: esriFieldTypeString, Alias: Match Level)
North_Lat (Type: esriFieldTypeString, Alias: North_Lat)
South_Lat (Type: esriFieldTypeString, Alias: South_Lat)
West_Lon (Type: esriFieldTypeString, Alias: West_Lon)
East_Lon (Type: esriFieldTypeString, Alias: East_Lon)
Address Fields:
SingleKey ( type: esriFieldTypeString , alias: Key , required: false , length: 100 )
Single Line Address Field:
Single Line Input ( type: esriFieldTypeString , alias: Key , required: false , length: 100 )
Candidate Fields:
Shape ( type: esriFieldTypeGeometry , alias: Shape , required: false )
Score ( type: esriFieldTypeDouble , alias: Score , required: false )
Match_addr ( type: esriFieldTypeString , alias: Match_addr , required: false , length: 120 )
Ref_ID ( type: esriFieldTypeString , alias: Ref_ID , required: false , length: 40 )
Addr_type ( type: esriFieldTypeString , alias: Addr_type , required: false , length: 20 )
I wondered if you ever got an answer to this one, or more importantly if you can recall the answer?
Is this perhaps the ESRI Geocoder dijit address field issue? The geocoder dijit is hardcoded to look for "SingleLine" in the query sent via JSON. In Steve's code it is "SingleKey".
Kelly posted a workaround for this. It is posted in this thread. Example code is there as well:
http://forums.arcgis.com/threads/75070-Geocoder-dijit-in-JS-API-v3.3-bug-quot-SingleKey-quot-vs-quot...