we have created a web map and shared the map with WebApp Builder with launchpad template. we configured the print template with default values. when we print the map you can see the map in the pdf and legend you can see the correct symbols but only the item names "Override 1" "Override 2" etc is displaying.
Please see the attachment
A more general Q: when these matters go unresolved for so long, what is the next step in the use-of-force continuum? It seems others have had this issue for many years, and it has largely gone ignored, or met with esoteric and arcane suggestions, with no response for clarity when asked.
I'm intelligent enough to deploy & use most of the features from 3.22 & up to present release; why not fix this in the API, or at least give a clear work-around?
Hi Dave,
This issue is being actively worked on with the 10.6 print service. We are in the process of verifying fixes and hope to have this addressed in an upcoming release of ArcGIS Online.
-Kelly
Hi Kelly,
To confirm, users of the JS API [as of this writing version 4.6] invoke the 10.6 print service with the PrintTask? I'm only familiar with the developer API, and don't know how the 2 communicate.
Any estimate when 10.6 will be released? I will get asked this question by the user and need to provide accurate info.
Thanks!
-Dave
Hey David,
ArcGIS Enterprise is available at 10.6 currently. The default print service for ArcGIS Online has not been upgraded to the next version yet. We hope to do this in the next release or two. I will update this post with updates when possible.
Is it possible to manipulate/change the print widgets item name/label using the JS API? Not about this specific "Override1" issue but generally changing the display name that appears on the print layout of the printer.
Mehretab
I found this problem when I need to print map contain WFS Layer. The legend print Override 1 text with the symbol of added layer.
Somebody can tell what is solution? Wait esri supporter for answer longtime.
This is an extremely frustrating issue.
I've spent a good few days working around the lazy SceneView implementation of printing ("printing"; it's a glorified screenshot).
After getting a 3D SceneView to send all layers, scene, and data to the print service and successfully return a pdf (like it should in the first place), I get "Override 1, Override 2" in my legend. I do some research, and find multiple threads saying this bug has existed for years, with these customers getting bug tickets lost and shuffled about, not getting any answer whatsoever.
To add, I'm using SceneView as a work around to get dynamically visible labels. So I am going on 3 workarounds deep for labels, printing, and legends.
I'm adding to this thread to indicate it is a serious issue. We pay a small fortune for Enterprise Server and a ton of other arcgis products. As a developer, I now have to explain why I can't get a legend labelled in a map if they don't want it named "Override 1", which to any reasonable person, seems like it should be such a trivial issue.
It doesn't matter if I'm passing ThisLayer[], ThatLayer[], TheCollection[], etc. A legend is a basic, fundamental mapping concept. It should just work. Look at this -> The Oldest Known Map of the World - Geography Realm It is a map with a legend and labels. It is technically more comprehensive than what my map print service gives me. It is from 500BC. it is currently 2019AD.
Has this been resolved? This is extremely frustrating.
No, it has not. It just gets kicked down the "it's a known issue" road, someone tries to generate a "ticket", and it gets lost.
It's a pretty special feeling being in a meeting with a client as a software developer (not just a GIS developer) and trying to explain in non technical terms why the legend says "Override 1" when they want to print a map of THEIR data. It is such a painfully obvious bug and I just simply don't understand why it can't be fixed. It seems like such an incredibly trivial issue and it makes you feel like you're garbage at programming to a client or your boss when you try to explain it.
Thanks again for stonewalling an explanation esri :thumbsup:
if it helps (more than likely not), I submitted a ticket for more clarification on this issue. I was told that this is a KNOWN ISSUE that should be fixed on the next release of the print service. I noticed some prior comments about there being a release "soon" but that was back in 2018.
I was told that there is no tentative date for the update, but only that it will happen eventually. Apparently the work around is to publish directly from ArcMap or ArcGIS Pro to retain the symbology and legend definitions.
Thank you for the workaround link, and following up.
Unfortunately, I need to have the js api send a custom layer on the fly to the print service as a convenience for the user. I could have a great map created by our GIS department, legend labels and all, but that defeats the purpose of a web app print service.
Again, thanks for the follow-up. You are more optimistic than myself regarding it getting fixed
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.
