Select to view content in your preferred language

Enhanced Search Result: "Override 1"

5123
14
06-01-2016 06:23 AM
JamesCrandall
MVP Frequent Contributor

Search results added to the legend as operational layers correctly display the service name it originated from.  However, when sending to a print task (as a pdf or any other output type), it renames this to "Override 1" in the legend of the print.

Has anyone been able to at least modify this name to something specific?  Any suggestions on where to begin?

Thanks!

Tags (2)
0 Kudos
14 Replies
davetinkle
Occasional Contributor

many months later, i now have a ticket/bug number: BUG-000114062

it's worth pointing out this has been a bug for half a decade!

again I ask: does *anyone* here have a work-around?

0 Kudos
VictorTey
Esri Contributor

I am not sure if this is relevant but a colleague managed to find a workaround to implement custom  legend for graphic layer

 

 const symbol = this._generateFillSymbol(2, new Color([0, 0, 0, 1]), new Color([192, 192, 192, 0.5]));
        const geometryBuffer = geometryEngine.geodesicBuffer(geometry, distance, units);
        const bufferAreaGraphic = new Graphic(geometryBuffer, symbol);
        this.bufferGraphicLayer.add(bufferAreaGraphic);
        const simpleJson = {
          'type': 'simple',
          'label': 'Area Buffer',
          'symbol': symbol.toJson()
        };

        const renderer = new SimpleRenderer(simpleJson);
        bufferAreaGraphic.symbol = null;
        bufferAreaGraphic._layer.setRenderer(renderer);
        bufferAreaGraphic._graphicsLayer.setRenderer(renderer);

 

. Code snippet attached. Hopefully it may help someone as it had helped me. 

RobertScheitlin__GISP
MVP Emeritus

Victor,

   This is a workaround for the override_1 label/text in the legend of the print task?

0 Kudos
VictorTey
Esri Contributor

Hi @RobertScheitlin__GISP  , Yes i can confirm it works for me. Legend is showing "Area Buffer" instead of Override 1

RobertScheitlin__GISP
MVP Emeritus

Great I will look into integrating this into the eSearch code base then.

0 Kudos