topic Re: Print widget showing labels for layers that are turned off in ArcGIS Experience Builder Questions

Print widget showing labels for layers that are turned off

KatiePhillips_ODNR — Fri, 23 Jan 2026 12:49:24 GMT

Hello,

We came across an issue recently where our user wanted to print a PDF from the current map extent within an Experience Builder we created. The PDF that was produced showed labels for layers that were turned off in the map. Another issue is the user was at an extent where the labels were not turned on (if they zoomed in further, the labels would be visible) and when they printed the map, the labels were visible in the PDF (which was not what they wanted).

Has anyone come across these issues? It seems like a bug. I did find something on if the print widget is nested in a widget controller if can cause these issues. I deleted the print widget and removed it from the widget controller and the issue persisted.

Below is an example of what I'm talking about. I circled a few of the labels that should not be there (they belong to a layer that is turned off) for reference.

Thank you,

Kate

Re: Print widget showing labels for layers that are turned off

ShengdiZhang — Tue, 27 Jan 2026 03:09:35 GMT

Hi @KatiePhillips_ODNR ,

When printing with the current map extent, the print scale differs from the map scale, and labels may be visible.

Could you reproduce this bug if choosing "Current Map Scale" for the map printing extents?

Thanks,

Shengdi

Re: Print widget showing labels for layers that are turned off

KatiePhillips_ODNR — Tue, 27 Jan 2026 13:50:23 GMT

Hi @ShengdiZhang,

I think I figured out the issue. In the AGOL webmap we set the symbology to focus on certain values, and we had the other values turned off.

For whatever reason the labels that were showing belonged to the "other" symbology that we had turned off. So, what I did was add a filter to the data to include only the values we wanted to display. This has seemed to fix the issue.

Its still strange that those labels were showing up when there was not a filter on the data. But at least we found a workaround.

Thank you for trying to help!

Kate