Enhanced Search Widget 2.5.0.8 - usage question

LisaArnold · ‎01-09-2012

Hello,

I am using the Enhanced Search Widget 2.5.0.8 with the compiled 2.5 viewer. I would like to use the userlist feature. I see my entered values in the drop down list, but when I try to search I get the following error: [RPC Fault faultString="Unable to complete operation." faultCode="400" faultDetail="Unable to complete query operation."] The field I am using this on does not have domain and or coded values set up, so I set usedomain to false. Does the field have to have a domain on it? My config is below, wondering if I just configured it wrong.

I am also getting a separate error with two other fields I am configuring to search. I would like to be able to search for ranges in my Hectares field. I would like to be able to search County name with either a partial name typed or upper or lower case letters used. I have done both of these things in version 2.4, but for some reason here on 2.5 am getting the error "Error #1010" when I try to search these two fields. Again, I am wondering if I have this configured incorrectly. My configuration is below. Thank you.

<expressions>
             
             <!--expression alias="Photo Year" textsearchlabel="Search Photo Year, 2004 or 2005">PhotoYr = [value]</expression-->
    <expression alias="Photo Year"
     textsearchlabel="Search Photo Year:"
     field="PhotoYr" usedomain="false" userlist="2004, 2005"
     >upper(PhotoYr) = upper('[value]')</expression>
    <expression alias="Report Year" textsearchlabel="Search Report Year, 2006 or 2010">ReportYr = [value]</expression>
    <expression alias="County"
     textsearchlabel="Search by County [ Example: San Juan ]:">upper(NAME) LIKE upper('[value]%')</expression>
    <expression alias="Hectares" textsearchlabel="Search Hectares">HECTARES = [value]</expression>
    <!--<expression alias="FieldYr Advanced Query" textsearchlabel="Enter SQL query, refer to documentation for examples">[value]</expression>
    <expression alias="State" textsearchlabel="Search by State [ Example: New Mexico ]:">upper(State) LIKE upper('[value]%')</expression>
    <expression alias="County" textsearchlabel="Search by County [ Example: San Juan ]:">upper(County) LIKE upper('[value]%')</expression>-->   
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Field Validation points</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>SITE</titlefield>
            <linkfield linkprefix="http://gis-web.heritage.unm.edu/gpd/reports/" linksuffix=".pdf">RptLink</linkfield>
   <icon isfield="false" iconprefix="" iconsuffix="">http://gis-web.heritage.unm.edu/gpd/images/page_white_acrobat.png</icon>
            <fields all="false">
    <field name="PHOTOYR" alias="Photo Year" gridfield="true" />
                <field name="ReportYr" alias="Report Year" gridfield="true" />
                <field name="HECTARES" alias="Hectares" gridfield="true"/>
                <field name="ACRES" alias="Acres" gridfield="true"/>
    <field name="NAME" alias="County" gridfield="true"/>
    
            </fields>

RobertScheitlin__GISP · ‎01-09-2012

Lisa,

Ok the userlist issue is likely this, dont' specify usedomain at all when you use userlist (something I probably need to fix in the code) and do not put a space in between the comma seperated values, no need to use the upper in the expression either:

<expression alias="Photo Year" textsearchlabel="Search Photo Year:"
                    field="PhotoYr" userlist="2004,2005">PhotoYr = '[value]'</expression>

For the county search I don't see an issue so I am not sure but try this:

<expression alias="County" textsearchlabel="Search by County [ Example: San Juan ]:">upper(NAME) LIKE upper('[value]')</expression>

You are going to have to give me some more details on the desire to search a range (and and example).

LisaArnold · ‎01-09-2012

Thanks for the quick response Robert.

I implemented both suggestions but am having the same errors still. I am using a secured service, but I don't think that is the issue due to the proxy being set to true, I am using a proxy page for security, and the search for Report year is working fine. I will keep trying to adjust things for these two, let me know if you have any other suggestions.

For the hectares range, when I did this on a previous version, users could type in a SQL expression in the search box, for example "HECTARES>1" or "HECTARES>5.5 AND HECTARES<10". This is the behavior I am trying to implement.

RobertScheitlin__GISP · ‎01-09-2012

Lisa,

Sorry I also missed that you should not specify the field in the expression either, so it should look like this:

<expression alias="Photo Year" textsearchlabel="Search Photo Year:"                     userlist="2004,2005">PHOTOYR = '[value]'</expression>

For the HECTARES expression if the user will actually type

"HECTARES>1" or "HECTARES>5.5 AND HECTARES<10"

than just use this expression:

<expression alias="Hectares" textsearchlabel="Search Hectares">[value]</expression>

Don't forget to mark the thread as answered by click the check under the promote demote icon

JustinFultz · ‎02-14-2012

Robert,

I am getting the same error as the initial poster. This occurs when I try to use a coded domain value on a feature class with a join in your eSearch widget version 2.5.0.6. I am using fully qualified names and have ObjectID and Shape fields visible in the service.

Here is my expression:

<expression alias="Operating Voltage" textsearchlabel="Select operating voltage..." field="SDE.SPP_Transmission.OPER_KV" usedomain="true" fromsubtype='false'>SDE.SPP_Transmission.OPER_KV = '[value]'</expression>

Any help you could provide would be appreciated.

By the way...This works fine on an old service I tested on without a join on the feature class.

Thanks,

Justin

RobertScheitlin__GISP · ‎02-14-2012

Justin,

You have to keep Up to date with the current version... Bugs are fixed once they are found and you will not get those fixes if you keep using an old version.

Though your issue is similar I will not dedicate time to answer questions that are tagged onto a thread that has already been answered. This is different than it use to be but, this is just the way it is going to be going forward.

The reason for requesting people start a new thread for each question is for many reasons:

It becomes very difficult to scan through a multi page thread and find an answer.

To many people hijack a thread with unrelated questions.

Now that the MVP program is functioning again. Points are awarded for each answered thread.

JustinFultz · ‎02-14-2012

Robert,

I apologize for the misplaced post. I am very appreciative of all you do for our user community!

I will update to the latest version and follow the proper protocol for all future posts.

Thanks!

Justin