eSearch URL search & print widget error

[CoryHines]

Good morning,

I am getting a funky error when trying to print when the url contains a search string.  It returns an error of 'esriJobFailed'.  I've poked around firebug and fiddler, but nothing really sticks out.

If I attempt to use the print widget from just my root url, everything works
http://gis.linncounty.org/maps
use 4901 Windmill Dr in the default address search and zoom to the result and print

If I attempt to use the print widget from the url that contains the search above it throws the error.
http://gis.linncounty.org/maps/index.html?search=191225300100000&slayer=0&exprnum=1&showdatagrid=fal...

Has anybody else seen this?  I've been able to reproduce this with the most current versions of IE and Firefox.

Thanks for any insight.

Cory

[RobertScheitlin__GISP]

Cory,

   First switch your PrintWidget.xml to use this url:

<taskurl>http://gis.linncounty.org/arcgis/rest/services/Utilities/PrintingTools/GPServer/Export Web Map Task</taskurl>

for some reason that print job url gives better error messages. Second for a temporary work around define sysbology for each layer in the eSearchWidget.xml

        <layer>
            <definitionexpression></definitionexpression>
            <enableexport>true</enableexport>
            <name>Subdivisions</name>
            <url>http://gis.linncounty.org/arcgis/rest/services/LandRecords/MapServer/18</url>
            <expressions>
                <expression alias="Subdivision Name" textsearchlabel="Search by Subdivision">
                    <values><value prompt="i.e. Bowman Woods">SUBDIVISIONNAME LIKE '[value]%'</value></values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Sections</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>SUBDIVISIONNAME</titlefield>
            <links></links>
            <fields all="false">
                <field name="SUBDIVISIONNAME" alias="Name" gridfield="true"/>
                <field name="TOWN" alias="City or Twp" gridfield="true"/>
                <field name="VOLUME" alias="Volume" gridfield="true"/>
                <field name="PAGE" alias="Page" gridfield="true"/>
                <field name="DATE_" alias="Date Recorded" gridfield="true" dateformat="MM/DD/YYYY"/>
            </fields>
            <zoomscale usegeometry="true" zoompercent="1.2"></zoomscale>
            <autoopendatagrid>true</autoopendatagrid>
            <symbology>
                <simplefillsymbol color="0x0000ff" alpha="0">
                    <outline color="0x0000ff" alpha="1.0" width="2" />
                </simplefillsymbol>
            </symbology>
        </layer>

[CoryHines]

Thanks Robert,

I just added the symbology tag to each layer and that seemed to fix the issue.  It made the highlighted layer yellow when it's printed for some reason, but I honestly could care less as long as it works.

I had seen this enhancement in the pdf you provide, but of course I never thought of adding it since I was ok with all my selections using the widgets selection color.

Glad it was a fairly simple fix.

Cory

[RobertScheitlin__GISP · Accepted solution]

Cory,

  Well that is actually a workaround for a bug I now have in the 3.0.14f version. I will get it resolved in the next version and you will not have to use that workaround. (Thanks Rhett for pointing me in the right direction of the error).

[CoryHines]

No worries!  I'll keep my eye out for the update.  Thanks again fellas!

[RhettZufelt]

Nice that you figured out that I had symbology set for one of my layers and not the other before I did 😉

Kind of weird with the yellow hightlight.  Like Cory said, no big deal, but I notice if I print with a selection from the esearch or selection (with glow filter removed) widgets, the cyan highlight (I have mine set to cyan) will be yellow on the print.
However, if I select one with the popup (click on it), I have the same selection color, but it prints as the same cyan you see in the selection.

R_

[RobertScheitlin__GISP]

Rhett,

  Actually the color of the selection in the print is not a surprise to me as the default for a Featurelayers selection color is Yellow. The likely hood is that Esri is handling the popups selection color in their code that is why you do not see that issue with their popup. To my knowledge this will be addressed in 3.1 API as they will allow you to set the alpha of the selection color or completely disable it.

[MegPeterson]

Hi Robert �??

Is it possible that the uncompiled 3.0.17f version did not include some of the bug fixes? I recently downloaded and extracted that version, but noticed the uncompiled folder did not extract. I manually copied the uncompiled folder from the .zip and added it to my project for editing, but the date for that folder was 8/3/2012.

Reason is I am running into bugs that the .txt file says have been fixed, mostly around the printing discussion in this post.

Figure 1 shows when I set the <symbols> for a purple outline, the pdf prints a yellow outline and blue solid fill.
Figure 2 shows the temporary fix as directed in this post �?? setting <symbology> on the individual layer. The pdf shows the yellow outline without the blue fill.

3.0.15 �?? 11/28/2012: shows issue fixed when printing after a search
3.0.17 �?? 1/11/2013: geometry service removed from .xml (but I still see it there)

Any ideas? I�??m at a loss. And thanks.

Running FlexViewer 3.0, SDK 4.6, ArcGIS Server 10.1

[RobertScheitlin__GISP]

Meg,

   The issue lies with esris print widget. I have told the API team of the issue and they are looking into it.

[MegPeterson]

Good to know - thanks for the response.

[MayJeff]

I having the same issue when try to upgrade on latest version (3.4 -7/22/13) but I have no problem when using this version (3.0.12-10/19/12).  Even though I changed the symbol using this:
<symbology>
      <simplefillsymbol color="0x0000ff" alpha="0">
                    <outline color="0x0000ff" alpha="1.0" width="2" />
       </simplefillsymbol>
</symbology>


Hope to solve this problem soon.

Thanks.