nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Print Widget fails when USA NAIP Natural Imagery layer in WAB app is checked on

AnitaB

Hi, all. I updated my Web Map to filter for NAIP YEAR = 2023 from YEAR = 2021. Ultimately, I readded the USA NAIP Natural Color Imagery layer completely, filtered for YEAR = 2023.

USA NAIP Imagery: Natural Color is set up in my WAB (launchpad) with Subscriber Content Access.

The Print Widget uses the default service URL.

When I test Print Widget, I get:

"Failed to create layer from service at https://...../rest/services/NAIP/ImageServer" as shown in the image below.

That is, if I have NAIP imagery turned on, printing to pdf fails. If the layer is off, the pdf is created.

Find more posts tagged with

Accepted answers

AnitaB

Hi. My work around with Tech Support was to make a copy of the NAIP imagery with subscriber content access in my name (she was surprised my initial scenario had been working at all prior to this date).

Once I subbed in this version of the NAIP layer into the map and WAB, my print widget worked as expected. I had to remember to go back and tweak other widgets in my app to allow for the new layer - easy enough. Thanks for the help!

All comments

LisaBerry

Hello and thank you for your question. I have forwarded this question to the development team and they were wondering if you can confirm if you are able to print the same content within Map Viewer Classic and the new Map Viewer in ArcGIS Online. This will help us narrow down where the issue is coming from.

AnitaB

Hi Lisa. Thanks for the response. I've attached the pdfs from my test.

Map Viewer - creates pdf
Map Viewer Classic (Map Only) - creates pdf
Map Viewer Classic (w/Legend) - creates pdf
and for fun - tried once more - WAB App - "Error, try again"

NAIP_Classic_wLegend.pdf

NAIP_Classic_MapOnly.pdf

NAIP_MapViewer.pdf

AnitaB

Lisa, I do wonder if it is this item that is the key to my troubles. A similar application with probably all the same data, but no "subscriber content access" for NAIP, does create a pdf from the Print Widget. Mine, as mentioned above:

USA NAIP Imagery: Natural Color is set up in my WAB (launchpad) with Subscriber Content Access.

AnitaB

Morning, Lisa! I thought I would post the latest twist in this adventure. This morning upon opening my WAB application I got the following message. Yesterday NAIP was displaying in the app.

It took me many iterations of back and forth-ing with test copies of the map and app to get rid of this message. Some combination of deleting and re-adding the NAIP layer (did this more than once as it didn't initially work, so not sure of its role in final fix), PLUS resetting the Request Limit and Interval on the subscriber content access removed the above error message. I was getting the proxy error many times as I experimented.

At the end of this morning what is (partially) working for me is

the NAIP layer, readded, with unchanged layer name, filtered for my desired year (2023)
the subscriber access request limit and interval set to unlimited/none. BUT, I had to fake it that I changed it and changed it back without OK in between. Otherwise, I got the proxy error and had to restart. I also saved the app after the initial unchecking of the settings. Then refreshed the app, faked out the settings, checked the box, and saved.

NAIP imagery displays once again in my application.

Alas, the Print Widget still doesn't work within the app.

HOWEVER, when in the app’s edit mode the Print Widget does work.

As an aside, this did correct the popup’s acquisition date display (it was working yesterday as well). The NAIP default popup configuration slipped its default formatting for the acquisition date. After this exercise, it is displaying properly.

Hope these tidbits are useful. thank you!

LisaBerry

I've been forwarding your replies to the development team and they believe this could be related to another bug. They recommend submitting a ticket through Esri Support so that this can be addressed. Thank you for reporting this behavior to the team so that it can be reviewed!

AnitaB

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.