Hello everybody,
I would like to include custom text elements in my layouts for ArcGIS Online WAB Print Widget. As our Server is on 10.3 and does not include the Get Layout Templates Info Task by default, I followed this blog:
https://blogs.esri.com/esri/arcgis/2016/06/20/printing-popups-from-web-application/
and used the python script from Github https://github.com/arcpy/sample-gp-tools/tree/master/GetLayoutTemplatesInfo
Both the export webmap and the Get Layout Templates Info task run and publish successfully fololwing the help http://server.arcgis.com/en/server/10.4/get-started/windows/tutorial-publishing-additional-services-... and the Get Layout Info shows my custom text elements (see attached).
Nevertheless, when I include my ExportWebmap Task in ArcGIS Online I can print, but the Custom Text Elements are not shown in the advanced tab.
There are no error messages and I have no idea where to start looking for a reason why this is not working.
Any help would be greatly appreciated!
Thank you Robert, I had not found the first one. Unfortunately there seemed to be no sulution to the Problem...
What I now did as a workaround is to modify the print widget so I can manually input the custom text elements.
While this works in general it has the drawback that my co-workers can't use this new widget in the built-in WAB and that I have to host the whole application on our Webserver only because of this - so any ideas concerning the original problem would be appreciated.
Sarah,
In your browsers web console do you see a warning "Get Layout Templates Info Error Error: Invalid URL" or any other error when using the print widgets advanced options button?
Back from holiday:
No unfortunately there are no warning messages to be found when I add the widget or when I use it. The fields just don't appear. I suspect the widget can't access the information from the Get Layout Templates Info but have no idea why.
Sarah,
Sorry I am drawing a blank then.
So, after upgrading to 10.4.1 and still having the same problem I did some more testing and finally got it to work.
The first of the following definitely was responsible, I am not sure about the second:
So this was not really a problem with the service but with my layouts.