Hello I was trying to configure the esearch widget to utilize our layers but when I run it I get: RPC Fault Fault String="Invalid or Missing input Parameters." faultCode="400" faultDetail=" Below is my code... Any help will be appreciated: ----------------------------------------------------------------------------- true APN http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0 APN LIKE '%[value]%' Use one of the graphical search tools to select Incidents true Parcel APN true true true Parcel Owner http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0 Owner LIKE '%[value]%' Use one of the graphical search tools to select Incidents true APN true true true Parcel Address http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0 ADDRESS LIKE '%[value]%' Use one of the graphical search tools to select Incidents true APN true true

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

esearch widget- RPC Fault Fault string=&quot;Invalid or Missing input Parameters

JayDira

Hello I was trying to configure the esearch widget to utilize our layers but when I run it I get:

RPC Fault Fault String="Invalid or Missing input Parameters." faultCode="400" faultDetail="

Below is my code...
Any help will be appreciated:
-----------------------------------------------------------------------------

<layers>

<layer>
   <definitionexpression></definitionexpression>
   <enableexport>true</enableexport>
   <name>APN</name>
   <url>http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0</url>

   <expressions>
    <expression alias="APN" textsearchlabel="Search by APN:">

     <values>
      <value prompt="Example: 181001490000 ">APN LIKE '%[value]%'</value>
     </values>
    </expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Incidents</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>Parcel APN</titlefield>
   <fields all="false">
    <field name="APN" gridfield="true" />
    <field name="OWNER" gridfield="true" />
    <field name="ADDRES" gridfield="true" />
    <field name="CITY" gridfield="true" />
    <field name="STATE" gridfield="true" />
    <field name="ZIP" gridfield="true" />

   </fields>
   <links></links>
   <zoomscale usegeometry="true" zoompercent="1.6" />
   <autoopendatagrid>true</autoopendatagrid>
   <relates></relates>
   <queryattachments>true</queryattachments>
</layer>

<layer>
   <definitionexpression></definitionexpression>
   <enableexport>true</enableexport>
   <name>Parcel Owner</name>
   <url>http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0</url>
   <expressions>
    <expression alias="OWNER" textsearchlabel="Search by Owner Name:">
     <values>
      <value prompt="Example: Joe Smith ">Owner LIKE '%[value]%'</value>
     </values>
    </expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Incidents</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>APN</titlefield>
   <fields all="false">
    <field name="APN" gridfield="true" />
    <field name="OWNER" gridfield="true" />
    <field name="ADDRES" gridfield="true" />
    <field name="CITY" gridfield="true" />
    <field name="STATE" gridfield="true" />
    <field name="ZIP" gridfield="true" />

   </fields>
   <links></links>
   <zoomscale usegeometry="true" zoompercent="1.6" />
   <autoopendatagrid>true</autoopendatagrid>
   <relates></relates>
   <queryattachments>true</queryattachments>
</layer>
<layer>
   <definitionexpression></definitionexpression>
   <enableexport>true</enableexport>
   <name>Parcel Address</name>
   <url>http://dbgis:6080/ArcGIS/rest/services/Parcels042012/MapServer/0</url>
   <expressions>

    <expression alias="ADDRESS" textsearchlabel="Search by ADDRESS:">

     <values>
      <value prompt="Example: 21825 Copley ">ADDRESS LIKE '%[value]%'</value>
     </values>
    </expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Incidents</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>APN</titlefield>
   <fields all="false">
    <field name="APN" gridfield="true" />
    <field name="OWNER" gridfield="true" />
    <field name="ADDRES" gridfield="true" />
    <field name="CITY" gridfield="true" />
    <field name="STATE" gridfield="true" />
    <field name="ZIP" gridfield="true" />

   </fields>
   <links></links>
   <zoomscale usegeometry="true" zoompercent="1.6" />
   <autoopendatagrid>true</autoopendatagrid>
   <relates></relates>
   <queryattachments>true</queryattachments>
</layer>

Encuentra más publicaciones etiquetadas con

Accepted answers

RobertScheitlin__GISP

Jay,

If your APN field is a numeric field than you need to adjust your SQL Expression for that use case:

<value prompt="Example: 181001490000 ">APN LIKE %[value]%</value>

Notice no single quotes tells the SQL that you are working with numbers.

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:

All comments

ScottLamon

Thanks Robert.

I found a few that were not correct and made the changes, but am still getting the error
This is how the fields appear in the rest endpoint:

Fields:

CONTRACT ( type: esriFieldTypeString , alias: CONTRACT , length: 30 )
LEGACY_NO ( type: esriFieldTypeString , alias: LEGACY_NO , length: 20 )
EFF_DATE ( type: esriFieldTypeString , alias: EFF_DATE , length: 8 )
EFF_DTE ( type: esriFieldTypeDate , alias: EFF_DTE , length: 36 )
TYPE ( type: esriFieldTypeString , alias: TYPE , length: 30 )
DESCRIPTION ( type: esriFieldTypeString , alias: DESCRIPTION , length: 40 )
GROSS_ACRES ( type: esriFieldTypeDouble , alias: GROSS_ACRES )
NET_ACRES ( type: esriFieldTypeDouble , alias: NET_ACRES )
PROSPECT ( type: esriFieldTypeString , alias: PROSPECT , length: 45 )
PROSP_NO ( type: esriFieldTypeString , alias: PROSP_NO , length: 10 )
COUNTY ( type: esriFieldTypeString , alias: COUNTY , length: 30 )
STATE ( type: esriFieldTypeString , alias: STATE , length: 2 )
AGENCY_NO ( type: esriFieldTypeString , alias: AGENCY_NO , length: 15 )
ASSET_AREA ( type: esriFieldTypeString , alias: ASSET_AREA , length: 45 )
BU ( type: esriFieldTypeString , alias: BU , length: 45 )
HERITAGE_CO ( type: esriFieldTypeString , alias: HERITAGE_CO , length: 3 )
EXP_DATE ( type: esriFieldTypeString , alias: EXP_DATE , length: 8 )
EXP_DTE ( type: esriFieldTypeDate , alias: EXP_DTE , length: 36 )
GRP_CODE ( type: esriFieldTypeString , alias: GRP_CODE , length: 3 )
STAGE ( type: esriFieldTypeString , alias: STAGE , length: 30 )
CNTY_CODE ( type: esriFieldTypeString , alias: CNTY_CODE , length: 3 )
FILE_NUM ( type: esriFieldTypeString , alias: FILE_NUM , length: 16 )
FILE_KEY ( type: esriFieldTypeInteger , alias: FILE_KEY )
SDE_UPDATE ( type: esriFieldTypeDate , alias: SDE_UPDATE , length: 36 )
LINK ( type: esriFieldTypeString , alias: LINK , length: 255 )
MAP_CODE ( type: esriFieldTypeString , alias: MAP_CODE , length: 3 )
LINKPREFIX ( type: esriFieldTypeString , alias: LINKPREFIX , length: 255 )
LINKSUFFIX ( type: esriFieldTypeString , alias: LINKSUFFIX , length: 255 )
SHAPE ( type: esriFieldTypeGeometry , alias: SHAPE )
OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
SHAPE.AREA ( type: esriFieldTypeDouble , alias: SHAPE.AREA )
SHAPE.LEN ( type: esriFieldTypeDouble , alias: SHAPE.LEN )

Link and SDE_DATE were the 2 I changed in the code to match the rest list.

RobertScheitlin__GISP

Scott,

Most of the time people encounter this error due to the incorrect spelling or CaSe of a field name in their list of fields. You need to double check the names of all the fields you have listed and their CaSe to see if they match your rest service directory. I can help with this part because your rest endpoint is not accessible to me.

ScottLamon

I've encountered a similar issue, and this type of thing is really not my forte. Any help would be greatly appreciated.

<!-- Contract -->
			<layer>

<name>Contracts</name>

<url>http://bvlwbip74.conoco.net/ArcGIS/rest/services/RPA_Maps/RPA_Land/MapServer/0</url>

	<expression alias="Number" textsearchlabel="Search Number [ Example: 255088 ]:">upper(CONTRACT) LIKE upper('%[value]%')</expression>
	<expression alias="Agency Number" textsearchlabel="Search Agency Number [ Example: 411753 ]:">upper(AGENCY_NO) LIKE upper('%[value]%')</expression>
	<expression alias="Prospect" textsearchlabel="Search Prospect [ Example: Little River ]:">upper(PROSPECT) LIKE upper('%[value]%')</expression>
	<expression alias="Type" textsearchlabel="Search Type [ Example: Forced Pooling Order ]:">upper(TYPE) LIKE upper('%[value]%')</expression>
	<!--expression alias="Date" textsearchlabel="Search Date [ Example: Forced Pooling Order ]:">upper(TYPE) LIKE upper('%[value]%')</expression-->

</expressions>

<graphicalsearchlabel>Use one of the graphical search tools to select</graphicalsearchlabel>

			<spatialsearchlayer>true</spatialsearchlayer>
			<titlefield>CONTRACT</titlefield>

</fields>

<icon isfield="false">assets/images/Livelink.gif</icon>

</layer>

JordanBaumgardner

First - Thank you so much. That was indeed my problem.
Second - Frackn grrrr. Spent 2 days chasing my tail. Should have asked for help sooner. The old config file had that, and I never questioned it.

Thanks again.

RobertScheitlin__GISP

Jordan,

In your attached REST Service directory text your fields are not listed with any xyz.somefield but that is how you have them in the eSearchWidget.xml. That is where I would start looking.

JordanBaumgardner

Folks, I'm having the same issue after an upgrade to 3.6

There is one query that worked (of course) in the old version and no longer works with my upgrade. I'm receiving the same error: Invalid or missing input parameters.

The table in question used to be in a <layer> tag, but it is not a feature class, and my understanding is that it should be moved to a <table> tag.

Of course the sample queries work great.

I'm beginning to think I need to set something up on the service itself, but I can't think of what that would be.

Here is my config entry:

Thank you in advance

  <table>
   <name>Customers</name>
   <token/>
   <definitionexpression></definitionexpression>
   <enableexport>true</enableexport>
   <url>http://gisweb:6080/arcgis/rest/services/detailed/MapServer/84</url&gt;
   <expressions>
    <expression alias="Location Code" textsearchlabel="Search Service by Location Code [ Example: 232410901 ]:" isvaluerequired="true">
     <values>
      <value prompt="Example: 232410901" isvaluerequired="true" >xyz.METER.LOCATION_CODE = '[value]'</value>
     </values>
    </expression>
    <expression alias="Customer Name" textsearchlabel="Search Customer by Customer Name [ Example: FROST ]:" isvaluerequired="true">
     <values>
      <value prompt="Example: FROST" isvaluerequired="true" >upper(xyz.METER.CUSTOMER_NAME) LIKE upper('[value]%')</value>
     </values>
    </expression>
    <expression alias="Billing Acct #" textsearchlabel="Search Customer by Account # [ Example: 487788 ]:" isvaluerequired="true">
     <values>
      <value prompt="Example: 487788" isvaluerequired="true" >xyz.METER.ACCOUNT_NUMBER = '[value]'</value>
     </values>
    </expression>
    <expression alias="Service Street Address" textsearchlabel="Search Customer by Street Address [ Example: 850 COMMERCE RD ]:" isvaluerequired="true">
     <values>
      <value prompt="Example: 850 COMMERCE RD" isvaluerequired="true" >upper(xyz.METER.SERVICE_ADDRESS_1) = upper('[value]')</value>
     </values>
    </expression>
   </expressions>
   <titlefield>xyz.METER.CUSTOMER_NAME</titlefield>
   <fields all="false">
    <field name="xyz.METER.LOCATION_CODE"/>
    <field name="xyz.METER.ACCOUNT_NUMBER" gridfield="true" />
    <field name="xyz.METER.CUSTOMER_NAME" gridfield="true" />
    <field name="xyz.METER.SERVICE_ADDRESS_1" gridfield="true" />
    <field name="xyz.METER.SERVICE_ADDRESS_2" gridfield="true" />
    <field name="xyz.METER.SERVICE_CITY_STATE_ZIP" gridfield="true" />
    <field name="xyz.METER.HOME_PHONE" gridfield="true" />
    <field name="xyz.METER.ACCOUNT_STATUS" gridfield="true" />
   </fields>
   <links/>
  </table>

Table in question:

Layer: xyz.METER (ID: 84)
Name: xyz.METER 
Display Field: CUSTOMER_NAME 
Type: Table 
Geometry Type: N/A 
Description: null 
Definition Expression: 
Copyright Text: N/A 
Default Visibility: false 
MaxRecordCount: 1000
Supported Query Formats: JSON, AMF
Supports Advanced Queries: true
Supports Statistics: true
Extent:
Drawing Info:
N/A
HasZ: false 
HasM: false 
Has Attachments: false 
HTML Popup Type: esriServerHTMLPopupTypeNone 
Type ID Field: null
Fields:
OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
LOCATION_CODE ( type: esriFieldTypeString , alias: Location Code , length: 30 )
METER_NUMBER ( type: esriFieldTypeString , alias: Meter Number , length: 30 )
CUSTOMER_NAME ( type: esriFieldTypeString , alias: Customer Name , length: 40 )
ACCOUNT_NUMBER ( type: esriFieldTypeString , alias: Account Number , length: 20 )
ACCOUNT_STATUS ( type: esriFieldTypeString , alias: Account Status , length: 10 )
BILLING_ADDRESS_1 ( type: esriFieldTypeString , alias: Billing Address 1 , length: 40 )
BILLING_ADDRESS_2 ( type: esriFieldTypeString , alias: Billing Address 2 , length: 40 )
BILLING_CITY_STATE_ZIP ( type: esriFieldTypeString , alias: Billing City, State, Zip , length: 40 )
SERVICE_DESC ( type: esriFieldTypeString , alias: Service Description , length: 40 )
SERVICE_ADDRESS_1 ( type: esriFieldTypeString , alias: Service Address 1 , length: 40 )
SERVICE_ADDRESS_2 ( type: esriFieldTypeString , alias: Service Address 2 , length: 40 )
SERVICE_CITY_STATE_ZIP ( type: esriFieldTypeString , alias: Service City, State, Zip , length: 40 )
HOME_PHONE ( type: esriFieldTypeString , alias: Home Phone Number , length: 40 )
SUBDIVISION ( type: esriFieldTypeString , alias: SUBDIVISION , length: 40 )
BLOCK_NUMBER ( type: esriFieldTypeString , alias: Block Number , length: 10 )
LOT_NUMBER ( type: esriFieldTypeString , alias: Lot Number , length: 10 )
APARTMENT ( type: esriFieldTypeString , alias: Apartment Number , length: 10 )
SUITE ( type: esriFieldTypeString , alias: Suite Number , length: 10 )
ON_DATE ( type: esriFieldTypeDate , alias: ON_DATE , length: 36 )
SECTION_ID ( type: esriFieldTypeString , alias: Line Section ID , length: 20 )
PRIMARY_METER ( type: esriFieldTypeString , alias: Primary Meter? , length: 1 , Coded Values:  ,  )
SERVICE_LOCATION_ID ( type: esriFieldTypeInteger , alias: Service Location ID (Foreign Key) )
CAYENTA_LOC_REC_NO ( type: esriFieldTypeString , alias: CAYENTA_LOC_REC_NO , length: 20 )
ROUTE_NO ( type: esriFieldTypeString , alias: Route No , length: 10 )
SEQ_NO ( type: esriFieldTypeString , alias: Sequence No , length: 10 )
CYCLE_NO ( type: esriFieldTypeString , alias: Cycle No , length: 10 )
JDE_WO_ID ( type: esriFieldTypeString , alias: JDE_WO_ID , length: 20 )
DATE_INSERVICE ( type: esriFieldTypeDate , alias: Date Inservice , length: 36 )
WIRE_COUNT ( type: esriFieldTypeInteger , alias: Wire Count )
SERVICE_STATUS ( type: esriFieldTypeString , alias: Service Status , length: 10 )
LOCATION_CLASS ( type: esriFieldTypeString , alias: Location Class , length: 10 )
LOCATION_SUBCLASS ( type: esriFieldTypeString , alias: Location Subclass , length: 10 )
METER_BILL_CODE ( type: esriFieldTypeString , alias: Meter Bill Code , length: 10 )
KW_DEMAND ( type: esriFieldTypeString , alias: KW Demand , length: 20 )
KWH_CONSUMED ( type: esriFieldTypeString , alias: KWH Consumed , length: 20 )
READ_DATE ( type: esriFieldTypeDate , alias: Read Date , length: 36 )
BILLING_CYCLE_DAYS ( type: esriFieldTypeString , alias: Billing Cycle Days , length: 10 )
CRITICAL_LOAD ( type: esriFieldTypeString , alias: Critical Load , length: 7 )
SPOT_LOAD ( type: esriFieldTypeString , alias: Spot Load , length: 5 , Coded Values:  ,  )
METER_TYPE ( type: esriFieldTypeString , alias: Meter Type , length: 15 )
METER_MULTIPLIER ( type: esriFieldTypeString , alias: Meter Multiplier , length: 5 )
TAX_DISTRICT ( type: esriFieldTypeString , alias: Tax District , length: 5 )
METER_COMMENTS ( type: esriFieldTypeString , alias: Meter Comments , length: 100 )
WORKREQUESTID ( type: esriFieldTypeString , alias: Work Request ID , length: 20 )
DESIGNID ( type: esriFieldTypeString , alias: Design ID , length: 20 )
WORKLOCATIONID ( type: esriFieldTypeString , alias: Work Location ID , length: 20 )
WORKFLOWSTATUS ( type: esriFieldTypeInteger , alias: Work Flow Status , Coded Values: [0: None] , [1: In Design] , [2: Pending Approval] , ...5 more... )
WORKFUNCTION ( type: esriFieldTypeInteger , alias: Work Function , Coded Values: [0: In-Service] , [1: Install] , [2: Remove] , ...5 more... )
HOUSE_NO ( type: esriFieldTypeString , alias: House Number , length: 18 )
STREET_PFX_DIR ( type: esriFieldTypeString , alias: Street Prefix Direction , length: 5 , Coded Values:  ,  , [NE: North East] , ...5 more... )
STREET_NM ( type: esriFieldTypeString , alias: Street Name , length: 40 )
STREET_NM_SFX ( type: esriFieldTypeString , alias: Street Name Suffix , length: 6 , Coded Values: [ALY: Alley] , [ANX: Annex] , [ARC: Arcade] , ...196 more... )
STREET_SFX_DIR ( type: esriFieldTypeString , alias: Street Suffix Direction , length: 5 , Coded Values:  ,  , [NE: North East] , ...5 more... )
SEC_ADDR_ID ( type: esriFieldTypeString , alias: Secondary Address (unit) , length: 5 , Coded Values: [APT: Apartment] , [BLDG: Building] , [BOX: Box] , ...12 more... )
SEC_ADDR_RANGE ( type: esriFieldTypeString , alias: Secondary Address Range , length: 18 )
SPECIAL_DIRECTIONS ( type: esriFieldTypeString , alias: Special Directions , length: 50 )
BAD_DOG ( type: esriFieldTypeString , alias: Bad Dog , length: 10 )
TECH_SERV_MULTIPLIER ( type: esriFieldTypeString , alias: Tech Services Multiplier , length: 10 )
FLEXNET_ID ( type: esriFieldTypeString , alias: FLEXNET_ID , length: 20 )
Relationships:
Service Location (0) -- Related To: De-Energized Service Locations (8)
Supported Operations:   Query   Query Related Records   Generate Renderer   Return Updates

RobertScheitlin__GISP

Jay,

There is a tag covered in the documentation called autoopendatagrid that should take care of your issue.

Not sure if you noticed or not but I moved your thread to the Flex Viewer forum out of the Flex API forum where you started it as all Flex Viewer and or widget questions belong here and not in the API forum.

JayDira

Thanks Robert it worked.
Thank you for all your help...I just have one last thing.

The show result on grid always pop up automatically after each search.
Is there a way to disable it, until I click the "Show Results on Grid" button"
Thanks.

Never mind I figured it out.
Thanks for all your help.

JayDira

Jay,

If your APN field is a numeric field than you need to adjust your SQL Expression for that use case:
<value prompt="Example: 181001490000 ">APN LIKE %[value]%</value>
Notice no single quotes tells the SQL that you are working with numbers.

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:

Thanks Robert it worked.
Thank you for all your help...I just have one last thing.

The show result on grid always pop up automatically after each search.
Is there a way to disable it, until I click the "Show Results on Grid" button"
Thanks.

RobertScheitlin__GISP

Jay,

If your APN field is a numeric field than you need to adjust your SQL Expression for that use case:

<value prompt="Example: 181001490000 ">APN LIKE %[value]%</value>

JayDira

Jay,

The only thing that jumps out at me when I quickly scan your xml is the fact that you have this SQL expression
ADDRESS LIKE '%[value]%'
and then you have the field name listed as ADDRES (notice on less S).

Thanks Robert...
That did the trick where I do not get the RPC error.

Now when I run the search and provide a APN, I do not get any result.
"Features selected: 0"

Not sure what I may be missing.
Thanks again with your quick reply.

JayDira

RobertScheitlin__GISP

Jay,

The only thing that jumps out at me when I quickly scan your xml is the fact that you have this SQL expression

ADDRESS LIKE '%[value]%'

and then you have the field name listed as ADDRES (notice on less S).

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.