Identify 2.5.3 - Limit by map service and proxy setup

[SimonRoss_User]

I'm trying to use the identify widget 2.5.3 but having a couple of issues that may or may not be solvable with the default configuration.

We have an application with three operational layers (all dynamic map services) and three base maps layers (all ESRI standard services).

For two of the operational layers we have pop-ups configured but for the other (which has 50+ layers) we'd prefer just to use the identify tool with all layers automatically setup (i.e. <layers onlythese="false">).  Currently when running the identify we're only getting results from the basemap layers which we have no interest in.  Not getting anything from our operational layers (presumably because proxy is incorrectly configured.

So my first question - to get up and running with the proxy - what exactly should go in the <name> tag - All layers are inside at least one group layer which I presume may have some impact on syntax.  Ideally we'd just want to specify proxy by service rather than individual layer.

My second question which relates to the first would be is it possible to limit the tool by service rather than by layer - I'm happy with the default identify settings but don't want to get information about basemaps, just the operational dynamic service.

Presuming this may not be existing functionality I'm happy to dive into the code and make some adjustments but thought I'd double-check here first and look for any pointers - overall a great looking tool, just needs tweaking a little for our use
Thanks

Simon

[RobertScheitlin__GISP]

Simon,

   You will find that esri use layer and map service interchangeably.  When it comes to the proxy capability of my widget layer more accurately means map service. But when it come to the Layers element and child layers it DOES mean individual Map Service layers. To answer your question about limiting my map service the answer is no, currently you can only limit by individual map service layers not the whole map service.

Don't forget to click the Mark as answer check and to click the top arrow (promote) as shown below:

[SimonRoss_User]

Simon,

   You will find that esri use layer and map service interchangeably.  When it comes to the proxy capability of my widget layer more accurately means map service. But when it come to the Layers element and child layers it DOES mean individual Map Service layers. To answer your question about limiting my map service the answer is no, currently you can only limit by individual map service layers not the whole map service.

Don't forget to click the Mark as answer check and to click the top arrow (promote) as shown below:

Robert,

Thanks for the quick response and clarification.  I've still however been unable to get this working as there is still some uncertainty over correct syntax.

1. For the proxy what is the requirement for the name, is it the full rest endpoint URL, the layer label in the main config file or some portion of the rest URL

2. For the individual layer configuration what happens if there are layers that have the same name either in one service or across different services - can this be captured somehow in the name definition (e.g. include group layer, include rest id or include service name) or is it simply not designed to accomodate that scenario.

Thanks

Simon

[RobertScheitlin__GISP]

Simon,

1.   It is the name of the mapservice as specified in the label inside the main config.xml for the Viewer.


2. I actually have not run into that situation with anyone so don't know the answer.

[SimonRoss_User]

Simon,

1.   It is the name of the mapservice as specified in the label inside the main config.xml for the Viewer.


2. I actually have not run into that situation with anyone so don't know the answer.

Robert,

Thanks for the response - it took me a while to find the time to revisit this and I'm still not having any success

Here's the excerpt from my main config.xml

<layer type="dynamic" label="BASE DATA" url="https://XXXX" visible="true" useproxy="true" imageformat="png24"/>
<layer type="dynamic" label="SENSITIVITIES" url="https://XXXX" visible="true" useproxy="true" imageformat="png24"/>
<layer type="dynamic" label="ROUTES" url="https://XXXX" visible="true" useproxy="true"/>
<layer type="feature" label="Markup Areas" url="https://XXXX" visible="true" useproxy="true" alpha="0.6" popupconfig="popups/PU_Markup.xml"/>


Here's my entry in the identifywidget.xml
<useproxy>
  <proxylayer>
   <name>ROUTES</name>
  </proxylayer>
</useproxy>
<layers onlythese="true">
  <layer>
   <name>Same as in REST</name>
   <fields>Id,Shape_Length</fields>
  </layer>
</layers>

I also tried inserting <useproxy>true</useproxy> in the layer tag element as this was required to get your enhanced search widget to work.  I'd really like to use this as I love the functionality but just cannot get it operating.  Any further thoughts or where I'm going wrong?
Thanks

Simon

[RobertScheitlin__GISP]

Simon,

    I personally don't use secure services and have no experience with them.