Select to view content in your preferred language

Widget Search Error

2584
8
Jump to solution
05-13-2013 07:24 PM
YanuardiHerdiyono
Emerging Contributor
Dear All,

I got message like this "[RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail=""]" when used search widget. Now I'm using flex viewer 3.1 and the data from joint table. When I remove the joint table, its work. So how to use search widget from joint table data? Thanks before..

-yanuardi
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
RobertScheitlin__GISP
MVP Emeritus
yanuardi,

   When you do a Search on a joined layer you need to use the full name of the joined field in your fields list and/or expression (i.e. dbo.main.field1)

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:

View solution in original post

0 Kudos
8 Replies
RobertScheitlin__GISP
MVP Emeritus
yanuardi,

   When you do a Search on a joined layer you need to use the full name of the joined field in your fields list and/or expression (i.e. dbo.main.field1)

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
RobertScheitlin__GISP
MVP Emeritus
yanuardi,

  You missed the most important step so let me tryout my new step by step graphic:

0 Kudos
YanuardiHerdiyono
Emerging Contributor
Dear rscheitlin,

I have done with this:

<configuration>
    <zoomscale>50000</zoomscale>
    <shareresults>false</shareresults>
    <layers>
        <layer>
            <name>Nama Sumur</name>
            <url>http://myserver:6080/arcgis/rest/services/PureGDB/MapServer/1</url>
            <expression>upper(geodatabase.DBO.sp_well.well_name) like upper('%[value]%')</expression>
            <textsearchlabel>Isi Nama Sumur</textsearchlabel>
            <titlefield>geodatabase.DBO.sp_well.well_name</titlefield>
            <fields>
                <field name="geodatabase.DBO.sp_well.well_name" alias="Well Name"/>
                <field name="geodatabase.DBO.sp_well.well_status_id" alias="Well Status"/>
            </fields>
            <orderbyfields>geodatabase.DBO.sp_well.well_name</orderbyfields>
        </layer>
    </layers>
</configuration>

Its true?


yanuardi,

   When you do a Search on a joined layer you need to use the full name of the joined field in your fields list and/or expression (i.e. dbo.main.field1)

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
RobertScheitlin__GISP
MVP Emeritus
Yanuardi,

   I have never seen anything in front of DBO before so you should check your field names again. The best way to do this is type http://myserver:6080/arcgis/rest/services/PureGDB/MapServer/1 in the address bar of your browser and this will take you to the REST Service directory page for that service, scroll down to the fields listing and you will see the fields listed like this:

Fields:

  • Parcels3.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )

  • Parcels3.TMP_NO ( type: esriFieldTypeString , alias: Temp Number , length: 23 )

  • Parcels3.MIN_CALC_ACRES ( type: esriFieldTypeDouble , alias: Minimum Calculated Area )

  • Parcels3.PPIN ( type: esriFieldTypeString , alias: PPIN , length: 6 )

  • Parcels3.PARCEL_NUMBER ( type: esriFieldTypeString , alias: Parcel Number , length: 29 )

  • Parcels3.OLD_NEW_FLAG ( type: esriFieldTypeString , alias: Old or New Flag , length: 1 )

  • Parcels3.NAME ( type: esriFieldTypeString , alias: Name , length: 40 )

  • Parcels3.ADDRESS_1 ( type: esriFieldTypeString , alias: Address Line 1 , length: 30 )

  • Parcels3.ADDRESS_2 ( type: esriFieldTypeString , alias: Address Line 2 , length: 30 )

  • Parcels3.ADDRESS_3 ( type: esriFieldTypeString , alias: Address Line 3 , length: 30 )


Those are the field names you would want to use.
0 Kudos
YanuardiHerdiyono
Emerging Contributor
Dear Robert,

My data like this:

Fields:

    geodatabase.DBO.sp_well.OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
    geodatabase.DBO.sp_well.well_id ( type: esriFieldTypeSmallInteger , alias: Well ID )
    geodatabase.DBO.sp_well.well_name ( type: esriFieldTypeString , alias: Well Name , length: 50 )
    geodatabase.DBO.sp_well.cluster_id ( type: esriFieldTypeSmallInteger , alias: Cluster ID )
    geodatabase.DBO.sp_well.field_id ( type: esriFieldTypeSmallInteger , alias: Field ID )
    geodatabase.DBO.sp_well.well_status_id ( type: esriFieldTypeSmallInteger , alias: Well Status )
    geodatabase.DBO.sp_well.SHAPE ( type: esriFieldTypeGeometry , alias: SHAPE )
    PURe.dbo.well_info.well_character ( type: esriFieldTypeString , alias: Well Character , length: 50 )
    PURe.dbo.well_info.rig_name ( type: esriFieldTypeString , alias: Rig Name , length: 50 )
    PURe.dbo.well_info.final_td ( type: esriFieldTypeDouble , alias: Final TD )
    PURe.dbo.well_info.max_tvd ( type: esriFieldTypeDouble , alias: Maximum TVD )
    PURe.dbo.well_info.start_easting ( type: esriFieldTypeDouble , alias: Start Easting )
    PURe.dbo.well_info.start_northing ( type: esriFieldTypeDouble , alias: Start Northing )
    PURe.dbo.well_info.end_easting ( type: esriFieldTypeDouble , alias: End Easting )
    PURe.dbo.well_info.end_northing ( type: esriFieldTypeDouble , alias: End Northing )
    PURe.dbo.well_info.coordinate_system ( type: esriFieldTypeString , alias: Coordinate System , length: 80 )
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Yanuardi,

   Well it looks like what you posted in in your earlier thread should work then.
0 Kudos
YanuardiHerdiyono
Emerging Contributor
Yanuardi,

   Well it looks like what you posted in in your earlier thread should work then.


<textsearchlabel>Search Intersection  [ Example: 2ndst and 4th st ]:</textsearchlabel>

Robert,

I still got error message "[RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail=""]"..
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Yanuardi,

   I would go to the REST Service Diresctory page (as I instructed before) and test your query by clicking the query link at the bottom of the page and filling in the web form with the fields and SQL expression. Maybe doing it from the web form will shead some light on what is going wrong.
0 Kudos