Select to view content in your preferred language

Flex Viewer 3.4 Search Widget Error

1331
7
Jump to solution
09-13-2013 08:07 AM
KevinHofmann
Emerging Contributor
I'm using ArcGIS Viewer for Flex3.4.  This search worked in previous versions but now it does not.
I've look at everything I can think and I'm still receiving the following error when running the search:
[RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail=""]
I'm sure I'm overlooking something simple but I can't see it.
I have other searches against string fields working on the same feature class/rest point.  The only difference with this search is that the field is a integer type:

DRAINAGEBASIN ( type: esriFieldTypeInteger , alias: Drainage Basin , Range: [-1, 999] )

Here is the search:
  <name>Drainage Basin GM</name>
            <url>URL LEFT OUT ON PURPOSE</url>
            <expression>DRAINAGEBASIN  = '[value]'</expression>
            <textsearchlabel>Drainage Basin (example: 453) =</textsearchlabel>
            <titlefield>FACILITYID</titlefield>
            <fields>
                <field name="FACILITYID" alias="Facility ID"/>
                <field name="SUBTYPE" alias="Subtype"/>
                <field name="YEARINSTALLED" alias="Year Installed"/>
                <field name="STATUS" alias="Status"/>
                <field name="POSITIONALACCURACY" alias="Positional Accuracy"/>
                <field name="DiameterFix" alias="Diameter (in.)"/>
                <field name="MATERIAL" alias="Material"/>
                <field name="SIZEDIMENSIONRATIO" alias="Size Dimension Ratio"/>
                <field name="RECORDEDLENGTH" alias="Recorded Length (FT)"/>
                <field name="UPSTREAMINVERT" alias="Upstream Invert (FT)"/>
                <field name="DOWNSTREAMINVERT" alias="Downstream Invert (FT)"/>
                <field name="SLOPE" alias="Slope (%)"/>
                <field name="DRAINAGEBASIN" alias="Drainage Basin"/>
                <field name="LINING" alias="Has a lining?"/>
                <field name="INSTALLEDCOST" alias="Installed Cost (LF)"/>
                <field name="GRAVITYINSPECTION" alias="TV Inspection"/>
                <field name="COMMENTS" alias="Comments"/>
                <field name="SOURCEDATA" alias="Source Data"/>
                <field name="HYPERLINK" alias="Record Drawing"/>
                <field name="VIDEOINSPECTIONDATE" alias="Video Inspection Date"/>
                <field name="VIEWCENTER_ID" alias="VIEWCENTER_ID"/>
                <field name="VERTICAL_DATUM" alias="Vertical Datum"/>
                <field name="CASING" alias="Casing?"/>
                <field name="SHAPE.len" alias="SHAPE.len"/>
            </fields>
            <orderbyfields>FACILITYID ASC</orderbyfields>

Any help would be greatly appreciated.
I'm thinking about creating a string field and copying the data (drainage basin values) over to it.
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
MichaelVolz
Esteemed Contributor
Kevin:

Are you getting your data from an SDE feature class?  If so, I think you should refer to the SHAPE.len field as SHAPE.LEN.  This is how an SDE field shows up when I investigate its REST properties.

View solution in original post

0 Kudos
7 Replies
RobertScheitlin__GISP
MVP Emeritus
Kevin,

   The problem is your expression. The single qoutes around [value] are for strings. When querying numbers you don't use single qoutes:

<expression>DRAINAGEBASIN  = [value]</expression>
0 Kudos
KevinHofmann
Emerging Contributor
Rob,

Thank you for the quick response.  I did remove the single quotes but I'm still receiving the same error message. 
I'm sure it's something else I've overlooked.
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Kevin,

   You will get that error when one of the fields you are specifying in your fields list does not exist. So check the spelling and punctuation of your field names.
0 Kudos
KevinHofmann
Emerging Contributor
Rob,

I will check that. Thanks for the help.

Kevin
0 Kudos
MichaelVolz
Esteemed Contributor
Kevin:

Are you getting your data from an SDE feature class?  If so, I think you should refer to the SHAPE.len field as SHAPE.LEN.  This is how an SDE field shows up when I investigate its REST properties.
0 Kudos
KevinHofmann
Emerging Contributor
It was the SHAPE.len field.

Thank you
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Kevin,

   Glad you got it worked out. Now you need to do your part on the forums.

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

0 Kudos