Select to view content in your preferred language

Problem with Query Expression in Enhanced Search Widget

1171
5
Jump to solution
09-11-2012 08:15 AM
MichaelVolz
Esteemed Contributor
In the Enhanced Search Widget, I have the following configuration where I am trying to query against a numeric field if the value is less than the user input value.

<value prompt="Example: Lower Range Assessed Value (AV) AV < 100000 - Just enter value" isvaluerequired="false">(PROP_ASSESS) < ([value])</value>

This is the error message I receive:

A problem occurred while parsing the configuration file widgets/eSearch/eSearchWidget_1.xml
Error #1095

If I have the following config value:

<value prompt="Example: Lower Range Assessed Value (AV) AV > 100000 - Just enter value" isvaluerequired="false">(PROP_ASSESS) > ([value])</value>

everything works fine.

Any idea what the problem could be?
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
RobertScheitlin__GISP
MVP Emeritus
Michael,

   Try this:

<value prompt="Example: Lower Range Assessed Value (AV) AV &lt; 100000 - Just enter value" isvaluerequired="false">PROP_ASSESS &lt; [value]</value>


The reason is the xml parser is thinking that that is the beginning of a new element

View solution in original post

0 Kudos
5 Replies
RobertScheitlin__GISP
MVP Emeritus
Michael,

   Here is what you need:

<value prompt="Example: Lower Range Assessed Value (AV) AV < 100000 - Just enter value" isvaluerequired="false">PROP_ASSESS &lt; [value]</value>


Don't forget to click the Mark as answer check on this post and to click the top arrow (promote).
Follow the steps as shown in the below graphic:

0 Kudos
MichaelVolz
Esteemed Contributor
Robert:

I am still getting the same error message.

Also, why does the > sign work but not the < sign?
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Michael,

   Try this:

<value prompt="Example: Lower Range Assessed Value (AV) AV &lt; 100000 - Just enter value" isvaluerequired="false">PROP_ASSESS &lt; [value]</value>


The reason is the xml parser is thinking that that is the beginning of a new element
0 Kudos
MichaelVolz
Esteemed Contributor
Robert:

Wouldn't the > sign also cause an error as it would make the xml parser think that that is the end of an element and the next element would not have the correct syntax?
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Michael,

   For some reason it handles that one correctly.
0 Kudos