topic WAB Printing Legend issues: Query Result Layer in ArcGIS Web AppBuilder Questions

WAB Printing Legend issues: Query Result Layer

MonikaHonkova2 — Mon, 18 Jan 2016 19:26:50 GMT

Hello,

I created a query using the Query widget and added the result as an operational layer to my map. The legend looks ok in the Legend widget but I don't understand why it's showing a label "Override 1" next to the legend patch in the printed map.

Also as you can see on the attached image, the symbol for the original map layer (polygon, no fill, pink outlines) is missing from the legend.

Is there a possible solution? Monika

Re: WAB Printing Legend issues: Query Result Layer

NedCake1 — Mon, 14 Mar 2016 20:27:19 GMT

Monika,

Did you ever find a solution for this issue?

Thanks

Ned

Re: WAB Printing Legend issues: Query Result Layer

NickToscano — Thu, 25 Aug 2016 17:44:22 GMT

As of today, 8/25/16, this is still an issue. Hard to find anything on this so I thought I'd reply here to keep attention to the issue.

ESRI Suggested work around

Publish the feature layer with a fill. Then make it hollow/transparent in the web app viewer.

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Sat, 20 Jan 2018 00:05:00 GMT

code snippet, please?

thanks.

Re: WAB Printing Legend issues: Query Result Layer

JustinPence2 — Fri, 15 Jun 2018 15:44:38 GMT

Issue still persists. It appears the outlines do not show for query results, on the fill.

Re: WAB Printing Legend issues: Query Result Layer

TanuHoque — Fri, 15 Jun 2018 16:58:16 GMT

FYI: this issue is fixed in 10.6 out of the box print service (i.e http://machine/arcgis/rest/services/Utilities/PrintTools/...) or if you publish a print service from ArcGIS Pro 2.1 to ArcGIS Server 10.6.

just for a quick try, you can use the following print service off a sample server:

http://sampleserver6.arcgisonline.com/arcgis/rest/services/Utilities/PrintingTools/GPServer/Export%20Web%20Map%20Task

What's new in ArcGIS Server 10.6 — Improved Print Service

Re: WAB Printing Legend issues: Query Result Layer

JustinPence2 — Fri, 15 Jun 2018 17:04:16 GMT

Good, to know, I am still on 10.5, so I'll need to upgrade in the future. Thanks

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Mon, 25 Jun 2018 13:43:15 GMT

Tanu,

Can you please provide a clear demonstration why you believe this is fixed? I used the sample server url as suggested, but as you can see in my attachment, it is not working.

Do you - or anyone else subscribed to this thread - know of a way to use the print service & get intended, bug-free results? Simply put, displaying "Override 1" is unacceptable, and no one appears to be motivated to explain what's gone wrong, and when it's going to be fixed. I have submitted my code to the support developers, and they have been able to reproduce my error, and did not have a work-around or advice if my coding was incorrect.

looking forward to your reply on my 2 questions.

Thanks.

Re: WAB Printing Legend issues: Query Result Layer

JustinPence2 — Wed, 25 Jul 2018 20:23:18 GMT

I think the symbology was fixed, specifically when there is a polygon involved, it now shows the outline. If my polygonal data did not have a fill and was completely transparent, the symbology would not appear in the legend. If it had a fill and and outline, the fill would show up, but not the outline. I think that issue is now fixed.

Labeling is a different story. The labeling appears to be fine for a normal web layer. When I run a query, I get the layer name with _QueryResult at the end. Speaking with a few of the engineers at the UC, this can't be changed yet...but might be in a future release. If "Override" isn't the actual layer name, and is of another error, I haven't experienced that yet. Wish I could be more help.

Re: WAB Printing Legend issues: Query Result Layer

TanuHoque — Mon, 30 Jul 2018 23:48:17 GMT

dave tinkle My apologizes for delayed response (somehow I didn't see the email notification of your reply).

Which client app did you use - is that a custom JS API app or WAB app? Either way, could you pls try with the latest version of that client app?

for custom JS API, pls update to its latest version

if it the map viewer from ArcGIS Online, then it should work as of today.

for on-premises Portal map viewer/Web App Builder, you need to upgrade to 10.6.1

Simply put, displaying "Override 1" is unacceptable, and no one appears to be motivated to explain what's gone wrong

In short, it was a side effect to work-around technical limitations with regards to color level transparency that was not supported by Windows GDI -- a print service heavily relied on GDI.

Print services, that get installed out of the box in 10.6 (or above) or when you publish your own print service from ArcGIS Pro 2.1 to ArcGIS Enterprise 10.6 (or above), don't rely on GDI at all hence you should not run into this issue.

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Tue, 31 Jul 2018 11:44:31 GMT

using JS API, and have upgraded every time in the hope someone would have fixed this. So that would make it 4.8 version. It's a known bug. I have a ticket. I don't know anything about GDI. All I know is I followed the API & printing a legend for a PDF is advertised as part of its core functionality, but it simply does not work.

Thanks.

Re: WAB Printing Legend issues: Query Result Layer

TanuHoque — Tue, 31 Jul 2018 16:51:24 GMT

Dave, sorry to hear that. Could you pls pass me your ticket #? and if possible, pls share the webmap_as_json string that gets sent to your print service from your app?

thanks.

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Wed, 01 Aug 2018 15:34:27 GMT

Unfortunately, our code has branched too many times to retrieve what was causing it to fail. It would be very disruptive to revert, compile, deploy, trap packets & put it here.

Don’t have a ticket number, but do have Case #02114883 & bug #BUG-000114062

Do you ask b/c you are part of the development team?

Re: WAB Printing Legend issues: Query Result Layer

TanuHoque — Thu, 02 Aug 2018 22:04:27 GMT

Thanks Dave for sharing the bug#. I took a look and I noticed you are using featureCollection instead of featureLayer, right?

Seems like there is an issue with featureCollection especially when it gets serialized into the json that gets sent to a print service. I have informed the appropriate team and they said they would take a look.

In the meantime, would it be possible to give it a try with a featurelayer (instead of a featureCollection)?

pls see the json below that uses featureLayer.

{ "operationalLayers": [{ "id": "dark-gray-base-layer", "title": "World Dark Gray Base", "opacity": 1, "minScale": 0, "maxScale": 0, "url": "https://services.arcgisonline.com/ArcGIS/rest/services/Canvas/World_Dark_Gray_Base/MapServer", "token": null }, { "id": "Cities", "title": "Cities", "opacity": 1, "minScale": 0, "maxScale": 0, "url": "https://services.arcgis.com/Wl7Y1m92PbjtJs5n/ArcGIS/rest/services/Californiaaa/FeatureServer/4", "token": null, "layerDefinition": {"drawingInfo": { "renderer": { "symbol": { "type": "esriSMS", "color": [0, 0, 0, 255], "xoffset": 0, "yoffset": 0, "size": 6, "style": "esriSMSCircle", "outline": { "type": "esriSLS", "color": [255, 255, 255, 255], "width": 0.5, "style": "esriSLSSolid" } }, "type": "simple" } } } }, { "id": "dark-gray-reference-layer", "title": "World Dark Gray Reference", "opacity": 1, "minScale": 0, "maxScale": 0, "url": "https://services.arcgisonline.com/ArcGIS/rest/services/Canvas/World_Dark_Gray_Reference/MapServer", "token": null }], "mapOptions": { "extent": { "spatialReference": { "latestWkid": 3857, "wkid": 102100 }, "xmin": -18971512.898950197, "ymin": 1292277.143967695, "xmax": -186348.82759027556, "ymax": 8004059.723630667 }, "spatialReference": { "latestWkid": 3857, "wkid": 102100 }, "scale": 73957190.948944 }, "exportOptions": { "dpi": 96 }, "layoutOptions": { "titleText": "Esri test reproduction", "authorText": "Esri", "copyrightText": "Esri inc", "customTextElements": [], "scaleBarOptions": { }, "legendOptions": { "operationalLayers": [{ "id": "Cities" }] } } }

... if you use this json as a value to WebMap_as_JSON parameter with the print service available on sampleserver6, and execute, you will get the following output.

please let me know if you have any question. Thanks.

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Fri, 03 May 2019 19:02:07 GMT

Tanu,

I delayed my response because I was assured this would be fixed in the next API release [how an unrelated Print service is related to an API release is still unclear to me].

I never used a FeatureCollection.

I have always used FeatureLayer.

To date, it still is NOT fixed, and does NOT appear to be correlated to the javascript API version, currently 4.11. I am using 4.6.

Please explain both

[1] why it isn't fixed, and feel free to correct me if it is

[2] if there is a work around so when I print [using the print task, NOT the print widget], my legend also prints. The end resultant PNG/PDF **must, must, must** have the legend on the final product.

Thanks.

Re: WAB Printing Legend issues: Query Result Layer

TanuHoque — Fri, 07 Jun 2019 23:06:48 GMT

Hi Dave,

apologies for the late reply. was extremely busy.

it appears to me that this bug might not have fixed yet. I have contacted JS API team and hope to get back to you soon.

Re: WAB Printing Legend issues: Query Result Layer

Noah-Sager — Mon, 10 Jun 2019 16:52:18 GMT

Hi Dave,

Sorry to hear about this ongoing issue. I'd like to investigate your use case and see where the trouble is.

Printing a FeatureLayer from a URL or portalItem should be fine. Printing a FeatureLayer from a Collection can be an issue. However, based on the screenshot supplied above, I believe what is being added to the map is a GraphicsLayer. Can you confirm?

I am currently looking into the Bug # and Case # that you referenced above to try to understand better.

-Noah

Re: WAB Printing Legend issues: Query Result Layer

davetinkle — Tue, 11 Jun 2019 16:09:27 GMT

[replied to email that assured me it would be posted here, but it did not, so i'm posting directly now w/ my emailed response from yesterday]

---------------------------------------------------

Hi Noah,

Using a FeatureLayer. Here’s the simple fn I wrote that first revealed the issue [not drop-in ready, but close enough]:

function printSubmit():

require(["esri/tasks/PrintTask", "esri/tasks/support/PrintTemplate","esri/tasks/support/PrintParameters", "esri/tasks/support/LegendLayer"],

function(PrintTask, PrintTemplate, PrintParameters, LegendLayer) {

disableButton('downloadButton','disableSubmitButton','canAddMapToCad','canAddToCad');

showDownloadProgressBar();

var pt = new PrintTask({

url: printTaskUrl

});

var template = new PrintTemplate();

var d = new Date();

var mm = d.getMonth() + 1; if (mm < 10) mm = '0' + mm;

var dd = d.getDate(); if (dd < 10) dd = '0' + dd;

var yyyy = d.getFullYear();

var legendLayers = [];

// for now, do not show legend, as there's a known bug where 'Override 1' is displayed, instead of layer id/store type description

// ref: https://community.esri.com/thread/170974 & https://community.esri.com/thread/101287

map.allLayers.forEach(function(item, i) {

if (item.declaredClass == "esri.layers.FeatureLayer") {

var l = new LegendLayer({

layerId: item.id,

title: " "

});

legendLayers.push(l);

}

})

template.layoutOptions = {

titleText: mapTitle,

authorText: "ALERT Report Generated: " + mm + "/" + dd + "/" + yyyy,

copyrightText: "SBU - Sensitive But Unclassified",

legendLayers: legendLayers

};

template.format = "png32";

template.exportOptions = {

width: $("#mapDiv").width(),

height: $("#mapDiv").height()

};

var pp = new PrintParameters();

pp.view = view;

pp.template = template;

pt.execute(pp).then(printComplete, printError);

})}

Hope this helps in your investigation. We’re still obliged to provide this service, so the ticket’s still valid. There is no workaround to the best of my knowledge.

Thanks.

Re: WAB Printing Legend issues: Query Result Layer

TUANNGUYEN1 — Mon, 24 Feb 2020 21:02:01 GMT

Has anyone had a final solution for this issue?

Re: WAB Printing Legend issues: Query Result Layer

LarsDe_Sloover — Tue, 09 Mar 2021 18:14:15 GMT

@Noah-Sager @TanuHoque

In the meantime, the fifth (!) anniversary of this issue has passed. Why is this problem still not resolved?