Will eSearch widget 2.4 version work with map service 10.22?

3817
3
Jump to solution
02-12-2015 02:46 PM
LeiZhou1
Occasional Contributor

We recently updated our map services to 10.22, I just change the url inside our SearchWidget.xml file and everything else is the same.  The eSearch Widget we use is 2.4 version.

All the parameters names and types are the same as before, we just use the new map services.  The codes are as below inside the eSearch Widget:

<expression alias="Permitted Flows Greater Than" textsearchlabel="Permitted Flows Greater or Equal to [Example:2.5]:">Permitted_Flow >= [value] & Permitted_Flow_Type = "MGD" </expression>
<expression alias="Permitted Flows Less Than" textsearchlabel="Permitted Flows Less or Equal to [Example:2.5]:">Permitted_Flow &lt;= [value] & Permitted_Flow_Type = "MGD" </expression>

Is there anything wrong with the codes? If they work well for the map service 10.01, why they suddenly are not working for 10.22? Thanks a lot!

0 Kudos
1 Solution

Accepted Solutions
RobertScheitlin__GISP
MVP Emeritus

Lei Zhou,

   On things I have seen numerous times is when people upgrade from 10 there is a tendency for the services field names to possibly change (Even if you did not make any changes to the MXD). So you need to look at all your field names for this map service and see if they are different then what you have in your XML.

View solution in original post

0 Kudos
3 Replies
RobertScheitlin__GISP
MVP Emeritus

Lei Zhou,

   On things I have seen numerous times is when people upgrade from 10 there is a tendency for the services field names to possibly change (Even if you did not make any changes to the MXD). So you need to look at all your field names for this map service and see if they are different then what you have in your XML.

0 Kudos
LeiZhou1
Occasional Contributor

I double checked the XML file and both old and new map services, our fields ARE the same as before including the data type.  Thanks!

0 Kudos
RobertScheitlin__GISP
MVP Emeritus

Lei Zhou,

   Well the only advice I have left is to use a http tool like Fiddler or Charles and check the http query request and result.

0 Kudos