<spatialreference>102100</spatialreference>
<spatialreference>102003</spatialreference>
<table> <name>Customers</name> <token/> <definitionexpression></definitionexpression> <enableexport>true</enableexport> <url>http://gisweb:6080/arcgis/rest/services/detailed/MapServer/84</url> <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
Anjelina, So when you click yes you do not recieve another dialog that asks you where you want to save the file? Is it possible that it is poping up behind another window?
Anjelina, Glad you got it working. 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:So are you saying that when you click the extract button you do not receive this dialog from the widget:
The Data Extract dialog box appears, prompting the end user to specify a location for saving the data subset.
Yes, I,m sure.
Anjelina, So when you are rested up and want to look at this again, make sure that your eSearchWidget.xml has<spatialreference>102100</spatialreference> and not <spatialreference>102003</spatialreference>
Eric, It was in version 3.x that this tag actually started being used. But as far as the case being mixed that was changed in the XML way back in 2.x, so you must have just updated an older XML for you to have had that issue.
Anjelina, Somehow I am beginning to doubt that you are actually following all the advice that people are giving you (and following it exactly to the letter). Can you check and see if the buffer is actually drawn but over near Africa at coordinates 0,0?
This is an error response returned from a GeometryService.Anjelina, could you use a tool like httpfox/firebug in Firefox, Chrome developer tools etc to see the actual request (the URL and the parameters) being sent by your application to your GeometryService?
[RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail="the input is not a geographic or projected coordinate system"]
Anjelina, So three things. Did you ACTUALLY check that your eSearchWidget.xml says:<spatialreference>102100</spatialreference> and not <spatialreference>102003</spatialreference>Did you start your geometry service on your new 10.1 server?Is the geometry service in your eSearchWidget.xml pointing to your new 10.1 geometry service?<geometryservice>http://localhost:6080/arcgis/rest/services/Utilities/Geometry/GeometryServer</geometryservice>
<geometryservice>http://localhost:6080/arcgis/rest/services/Utilities/Geometry/GeometryServer</geometryservice>
Anjelina, You need to change the spatialreference in the eSearchWidget.xml to match the WKID of your Map:<spatialreference>102100</spatialreference>
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.