Identify Widget for Flex Viewer - No Loading of Results in Application Preview

[RichardGeoghegan]

I have added the Identify Widget found at the following address;

http://www.arcgis.com/home/item.html?id=39cf66d58c234279ba728c50461a1a89


I have loaded two features into this tool in Widget settings and I chose the same URL for both of the feature layers which are found on my ArcGIS Server site. These are the same URLs I provided when adding these features as operational layers when beginning the Application Builder. When I preview my application the Identify Widget appears however when I click on one of the features which I added to the widget no results are loaded.

Any ideas as to what might be the issue?

[RobertScheitlin__GISP]

Richard,

   I just tested version 3.6.3 in App Builder and it work fine in the preview Tab. Is it just the preview tab? Does it work when you use the actual configured application? One thing to note is Flex is a case sensitive language so if you added your operational layers using a certain CaSe then you have to add that eXaCt case when configuring the layer in the identify widget GUI.

[RichardGeoghegan]

Robert it doesn't work in the configured application either. It must not be an issue with case differences either as the link I chose when loading the operational layers is the same in terms of case as the URL I chose in the widget settings.
There is one thing that concerns me is that the layers that I published to ArcServer were from an SDE database. This hasn't caused any problems when implementing the feature layers to the default widgets, could that be a possible cause of the problem in the identify widget?

[RobertScheitlin__GISP]

Richard,

   No, This widget has been around for years and 1000 of users are using SDE data. It is something in your configuration. It is just hard for me to say what. Can you zip up the main config.xml and your IdentifyWidget_#.xml (the one with the highest number) and attach it for me to review? The normal location to find these files would be "c:\inetpub\wwwroot\YOUR APPLICATION NAME\"

[RichardGeoghegan]

Robert here are those files. Thanks

[RobertScheitlin__GISP]

Richard,

  Well, case was not the issue as you said. There is nothing jumping out at me either.

1. Are these layers visible when you attempt to identify them?


2. What is the type of geometry for these layers?


3. Can you possibly do a screenshot of the REST Service directory page for layer id 0 'BlueFlagBeaches'? Or just copy the text and paste it into a text file and zip it.

[RichardGeoghegan]

Yes, these layers are visible when I attempt to identify them and they are point features. I attached the REST URL, is this correct?

[RobertScheitlin__GISP]

Richard,

   No that is not what I was looking for. This is what I was looking for

Layer: Schools (ID: 0)  Name: Schools

Display Field: SCHOOLNAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Definition Expression: N/A

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, AMF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Extent:

• XMin: 604569.1675482318

YMin: 1123900.0551555306
XMax: 730448.9172974639
YMax: 1247514.7957506552
Spatial Reference: 102629  (102629)

Drawing Info:

• Renderer:




• Unique Value Renderer:

Field 1: DISTRICT
Field 2: null
Field 3: null
Field Delimiter: ,
Default Symbol:



• N/A


Default Label: null
UniqueValueInfos:



• Value: CALHOUN COUNTY

Label: Calhoun County
Description:
Symbol:



• 






Transparency: 0
Labeling Info:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )


• SCHOOLNAME ( type: esriFieldTypeString , alias: SCHOOLNAME , length: 50 )


• STREET_NUM ( type: esriFieldTypeDouble , alias: STREET_NUM )


• STREET_NAM ( type: esriFieldTypeString , alias: STREET_NAM , length: 35 )


• CITY ( type: esriFieldTypeString , alias: CITY , length: 16 )


• STATE ( type: esriFieldTypeString , alias: STATE , length: 2 )


• ZIPCODE ( type: esriFieldTypeString , alias: ZIPCODE , length: 5 )


• PHONE ( type: esriFieldTypeString , alias: PHONE , length: 12 )


• NCES_ID ( type: esriFieldTypeString , alias: NCES_ID , length: 15 )


• STATE_ID ( type: esriFieldTypeString , alias: STATE_ID , length: 12 )


• DISTRICT ( type: esriFieldTypeString , alias: DISTRICT , length: 20 )


• SHAPE ( type: esriFieldTypeGeometry , alias: Shape )


• ccDistrict ( type: esriFieldTypeString , alias: Calhoun County School District , length: 25 )

Supported Operations:   Query   Generate Renderer   Return Updates

[RichardGeoghegan]

Sorry about that, here it is.

[RobertScheitlin__GISP]

Richard,

   Hmm... this is perplexing. can you go back into the identify widget GUI and change the "Only These Layers" to "Off" and try to identify again.