#legendDiv path{ fill-opacity:0.6 !important; }
sorry for the delayed reply. i did some more testing and confirmed that this is a REST problem (as opposed to a problem in the JS API). it seems that currently ArcGIS Server does not honor transparency defined as an alpha value within a RGB color symbol for feature service layers.
you can see this problem by removing the .TXT extension from the attached .webmap file (which has identical contents to the webmap JSON we pass to ArcGIS Server when printing) and dragging and dropping itdirectly into ArcMap."symbol" : { "color" : [0, 255, 0, 128], //128 (or 50% transparency) is replaced by 255 "outline" : { "color" : [0, 0, 0, 128], //128 (or 50% transparency) is replaced by 255 "width" : 2, "type" : "esriSLS", "style" : "esriSLSSolid" }, "type" : "esriSFS", "style" : "esriSFSSolid" },
even though an alpha transparency of 128 is specified for the symbol fill color, the layer is completely opaque in ArcMap
[ATTACH=CONFIG]25482[/ATTACH]
since your sample app passes a collection of graphics instead of a feature service layer, you get around this limitation (but encounter another).
ive asked the developers to update the Export Web Map Spec to acknowledge the limitation i found. sorry for the inconvenience.
Bill,
this is unfortunately still considered a known limit. i went ahead and logged an issue requesting that it be revisited in the future on your behalf.
[NIM099543: Add support for transparency in color's alpha value when printing feature layers.]
sorry for the inconvenience.
I'm having a similar problem - we have an application that is joining dynamic JSON data to a map service by a unique ID shared between the JSON dataset and the map service... everything works brilliantly in our application, although we ended-up creating a custom breaks function; however, when we "print" the map using the default template, the LegendLayer passed to the server ends-up overriding the break labels rendering in the application with "override 1", "override 2", etc., like what is seen in Daniel's attachment (exOverride.pdf).
The resolution, it seems from John Gravois' previous response, is to ensure the map service contains the field/data... unfortunately, this isn't an option for us. Has anyone had success with a workaround? My initial thought was to create a custom template where we could send an HTML object from the client-side (the object being the legend) - I haven't come across supporting documentation yet to pursue this... we are currently using the default print template.
Thanks!
Same issue here...UniqueValueRenderer with a function. Plopping a client-side legend into the print layout would be very handy.
Long-shot but, in the Print Template task the API can accept 'customTextElements' in the layout options. Is there some way to draw SVG and labels that could get put into a snapshot and inserted as png into the print output?
...coming up on 5 years and API version 4.6 still shows "Override 1" in the PDF print task output.
any fix, or even a work around?
any acknowledgement this is a bug, or a correction if not?
thanks.