I recently upgraded our Server from 10.1 to 10.2. I also took the opportunity to roll to the latest version of the Flex Viewer (3.6) from 3.4. Prior to upgrading the Server, I prepped the new viewer and everything was working great.
Once I upgraded the Server to 10.2, however, I now get an error when I attempt to do a search against my parcel layer. The error is "[RPC Fault faultString="Unable to complete operation." faultCode="400" faultDetail="An SQL statement with comments and/or semicolon is invalid."].
The parcel layer has joined Assessor data, but nothing changed with the map service (other than upgrading to 10.2) nor did I change anything in the eSearch config for this layer.
The relevant code block from the eSearch config is:
These queries have worked through multiple versions of the eSearch widget (with appropriate config file tag adjustments), so I am at a loss as to why there is suddenly an issue. Could the error be referring to something in the result set rather than the SQL query syntax itself?
FWIW, the same map service is successfully used in the Identify widget. A similar table of joined info is used with my site address layer and successfully performs search queries as expected. It uses the same database connection as the joined info in the parcel service.
I'm not sure if this is an eSearch issue or something with Server 10.2. Nothing in the "What's new in 10.2" seemed to indicate that esri did anything major with with SQL queries and map services, but that doesn't mean a minor change somewhere has created this issue.
Any thoughts?
Thanks.
Once I upgraded the Server to 10.2, however, I now get an error when I attempt to do a search against my parcel layer. The error is "[RPC Fault faultString="Unable to complete operation." faultCode="400" faultDetail="An SQL statement with comments and/or semicolon is invalid."].
The parcel layer has joined Assessor data, but nothing changed with the map service (other than upgrading to 10.2) nor did I change anything in the eSearch config for this layer.
The relevant code block from the eSearch config is:
Code:
<layer>
<token/>
<definitionexpression></definitionexpression>
<enableexport>true</enableexport>
<name>Parcels</name>
<url>http://server-name:6080/arcgis/rest/services/General_Mapservices/parcels/MapServer/2</url>
<expressions>
<expression alias="Parcel ID" textsearchlabel="Search by Parcel ID:">
<values>
<value prompt="Example: 2724069035">coivector.COI.Parcels.ParcelPIN = upper('[value]')</value>
</values>
</expression>
<expression alias="Owner Name" textsearchlabel="Search by owner name:">
<values>
<value prompt="">Assessor_Info.GISMAP.%ParcelInfo.PropertyOwner LIKE upper('%[value]%')</value>
</values>
</expression>
<expression alias="Plat Name" textsearchlabel="Search by Plat Name:">
<values>
<value prompt="Example: ENGLEWOOD ADD">coivector.COI.Parcels.PlatName LIKE upper('%[value]%')</value>
</values>
</expression>
<expression alias="Site Name" textsearchlabel="Search by site name:">
<values>
<value prompt="Example: GILMAN VILLAGE">Assessor_Info.GISMAP.%ParcelInfo.PropertyName LIKE upper('%[value]%')</value>
</values>
</expression>
<expression alias="Appraised Land Value" textsearchlabel="Search using appraised land value:">
<values>
<value prompt="include operator i.e. > 500000">Assessor_Info.GISMAP.%ParcelInfo.AppLandVal [value]</value>
</values>
</expression>
<expression alias="Appraised Improvements Value" textsearchlabel="Search using appraised improvements value:">
<values>
<value prompt="include operator i.e. > 1000000">Assessor_Info.GISMAP.%ParcelInfo.AppImprVal [value]</value>
</values>
</expression>
<expression alias="Total Appraised Value" textsearchlabel="Search using total appraised value:">
<values>
<value prompt="include operator i.e. > 2000000">Assessor_Info.GISMAP.%ParcelInfo.TotalAppVal [value]</value>
</values>
</expression>
<expression alias="Appraised Land Value-sq. ft." textsearchlabel="Search using appraised land value per sq. ft.:">
<values>
<value prompt="include operator i.e. > 90">Assessor_Info.GISMAP.%ParcelInfo.AppLandValSF [value]</value>
</values>
</expression>
<expression alias="Appraised Improvements Value-sq. ft." textsearchlabel="Search using appraised improvements value per sq. ft.:">
<values>
<value prompt="include operator i.e. > 200">Assessor_Info.GISMAP.%ParcelInfo.AppImprValSF [value]</value>
</values>
</expression>
<expression alias="Total Appraised Value-sq. ft." textsearchlabel="Search using total appraised value per sq. ft.:">
<values>
<value prompt="include operator i.e. > 200">Assessor_Info.GISMAP.%ParcelInfo.TotalAppValSF [value]</value>
</values>
</expression>
<expression alias="Commercial Building Gross Total Sq. Ft." textsearchlabel="Search using commercial building total gross sq. ft.:">
<values>
<value prompt="include operator i.e. > 500000">Assessor_Info.GISMAP.%CommBldg_GrossSF_by_PIN.CommBldgTotalGrossSF [value]</value>
</values>
</expression>
</expressions>
<graphicalsearchlabel>Use one of the graphical search tools to select parcels</graphicalsearchlabel>
<spatialsearchlayer>true</spatialsearchlayer>
<titlefield>ParcelPIN</titlefield>
<fields all="false">
<field name="coivector.COI.Parcels.ParcelPIN" alias="Parcel PIN" gridfield="true"/>
<field name="coivector.COI.Parcels.PlatName" alias="Plat Name" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.PropertyName" alias="Property Name" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.PropertyOwner" alias="Property Owner" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.OwnerAttention" alias="Owner Attention" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.OwnerAddress" alias="Owner Address" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.OwnerCityState" alias="Owner City-State" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.OwnerZipCode" alias="Owner ZipCode" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.Plat" alias="Plat" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.Lot" alias="Lot" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.Block" alias="Block" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.YearBuilt" alias="Year Built" gridfield="true" gridfieldonly="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.LotSF" alias="Lot Sq Ft" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.AppLandVal" alias="Appraised Land Value" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.AppImprVal" alias="Appraised Improvements Value" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.TotalAppVal" alias="Total Appraised Value" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.TotalAppValSF" alias="Total Appraised Value Sq Ft" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.AppLandValSF" alias="Appraised Land Value Sq Ft" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%ParcelInfo.AppImprValSF" alias="Appraised Improvements Value Sq Ft" gridfield="true"/>
<field name="Assessor_Info.GISMAP.%CommBldg_GrossSF_by_PIN.CommBldgTotalGrossSF" alias="Commercial Building Total Gross Sq Ft" gridfield="true"/>
</fields>
<icon isfield="false"></icon>
<links/>
<zoomscale usegeometry="true" zoompercent="2"></zoomscale>
<autoopendatagrid>false</autoopendatagrid>
</layer>FWIW, the same map service is successfully used in the Identify widget. A similar table of joined info is used with my site address layer and successfully performs search queries as expected. It uses the same database connection as the joined info in the parcel service.
I'm not sure if this is an eSearch issue or something with Server 10.2. Nothing in the "What's new in 10.2" seemed to indicate that esri did anything major with with SQL queries and map services, but that doesn't mean a minor change somewhere has created this issue.
Any thoughts?
Thanks.