Enhanced-Search-Widget-for-FlexViewer Part III

[RobertScheitlin__GISP]

All,

   Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

[DevonHedemark1]

Aaron,

I believe you are correct about 2.5 widgets not working with a 3.6 viewer. To clarify, I have downloaded the latest 3.6 compiled viewer, configured the main XML to hit our map services, and now am working on downloading and configuring the 3.6 widgets for the 3.6 viewer.  I work on the 3.6 viewer configuration on my production GIS server but staff is not hitting the URL to the 3.6 viewer so it is just a separate folder at wwwroot.  Our staff uses the 2.5 viewer I have up and running and then when I am done with the 3.6 version I will replace the links that staff hit.  I hope that makes sense.

I may look to work with the App Builder.  I have been scared to install Adobe AIR and App Builder on my GIS sever in case it causes issues with my production flex viewer 2.5 that I built without app builder.  I can take a snap of the GIS server as it is a VM so I will probably bite the bullet and install the App Builder.

Devon

[RobertScheitlin__GISP]

Devon,
   My advice is to completely forget what you had working in 2.5 and just start from scratch. One thing that sticks out to me is you have your fields listed as there is a join on this map service. if there is actually a join on this map service then any where you use a field it has to be the full field name.

i.e.

PIN like '[value]%'

should be:

publish.RDDGIS.PCLCOMP.PIN like '[value]%'

also FULLADDRESS is not even listed in the fields XML...

The titlefield also schould be usinf the full field name.

[DevonHedemark1]

Devon,
   My advice is to completely forget waht you hade working in 2.5 and just sart from scratch. One thing that sticks out to me is you have your fields listed as there is a join on this map service. if there is actually a join on this map service then any where you use a field it has to be the full field name.

i.e.

PIN like '[value]%'

should be:

publish.RDDGIS.PCLCOMP.PIN like '[value]%'

also FULLADDRESS is not even listed in the fields XML...

The titlefield also schould be usinf the full field name.

Hi Robert,

Yes, I will ignore what worked in 2.5 and focus on configuring 3.6.  Thanks for the insight. 

I have updated the syntax accordingly in my 3.6 esearch and 3.6 search widgets.  Here are the updated XML files and a couple screenshots of the results from the Search widget vs. the Esearch widget.  BOTH the XML's attached here are from compiled 3.6 widgets.  I still get only one result with the Esearch and two results with the search widget for the same PIN search.

Thanks for all your help and any further insight you may have.  Devon

[RobertScheitlin__GISP]

Devon,

   I am not sure if this is it but the more things you have configured incorrectly for the version 3.6 of this widget will add to possible issues. Links do not look the same same way as you have it configured in version 3.6. Links should look something like this now a days:

            <links>
                <link alias="link" disablelinksifnull="true" disableinpopups="false">
                    <![CDATA[{URL}]]>
                    <icon><![CDATA[{Icon_Link}]]></icon>
                </link>
            </links>

If this does not resolve the issue then try just setting the field:

<fields all="true" />

and remove all the other field xml stuff.

[DevonHedemark1]

Thanks Robert. 

I updated the link syntax accordingly and I also specified all fields as you recommended.  My link to the assesor map is working which is great.  But, I am still only returning one result with the Esearch widget and return two results for the same PIN search with the default 3.6 search widget.  I cleaned-up the XML to focus on the PIN search removing all the other configured searches.  Here is an updated XML and screenshot.

Thanks again for all the help.  Devon

[RobertScheitlin__GISP]

Devon,

  what is the PIN  field type and what is the value that you are entering in both the search and eSearch?

[DevonHedemark1]

Hi Robert,

The PIN field is string.  I have been using the same "test parcel" in both widgets with PIN number 102470018000.  I am only typing the numeric value with no quotes or anything else; just 102470018000.   I hope this helps.

Regards, Devon

[AaronKreag]

Robert,

I have a Flex app that has worked fine with Store.gis.ACCOUNTS.prop_id being a String.  The following line works great.

<value prompt="Example: 2095 (Numbers Only - Finds All)" isValueRequired="true">Store.gis.ACCOUNTS.prop_id LIKE '%[value]%' </value>

However, I now have a new table in which .prop_id is actually stored as an Integer, length 10.  I can not change the database/table but I still need to search the contents of this field like its a string.  Is there a way to use something like:


<value prompt="Example: 2095 (Numbers Only - Finds All)" isValueRequired="true"> CAST (Store.gis.ACCOUNTS.prop_id as VARCHAR(10)) LIKE '%[value]%' </value>

Just curious....  Thank you!  Aaron

[RobertScheitlin__GISP]

Aaron,

   The rule of thumb that I have figured out is if you cn get the SQL syntax to run in ArcMap then you are LIKELY to get it to use the same syntax on ArcGIS Server through the query task. Now your exact use case... I have not seen this done before.

[JuliaGalindo]

Hi to all,

I have downloaded the Esearch widget version 3.6.1 and added to the Arcgis viewer for flex application builder without problems (I erased the older one). But, when I compare all layers in the widget with those shown in the online example I am missing some layers, like the Calhoun Parcels. It looks like my application builder is looking to an older Esearch widget. 

I have already erase all esearch widgets I could find, I also erased the browser cache (although the application preview is being done in the application builder).  Does anyone knows if I am missing something?

Thanks,