Hi community,
I am looking to add print formats A0, A1, and A2 to the print widget in Experience Builder (EB). Alternatively, I am open to exploring any other solutions for integrating these formats within EB, possibly using JavaScript code.
Has anyone already implemented this enhancement or found a suitable workaround?
Any insights or examples would be greatly appreciated!
Isabelle
You haven't specified what EB environment you're working in- Portal or AGOL. If it's Portal based, you should be able to publish your own print templates and then specify that print service for the Print Widget. This link from the ArcGIS Server Help describes the process of publishing your own print templates.
It's in AGOL
Sharing from Pro may require a certain permission/account level. Several colleagues and myself ran into that blocker when trying to share these.
Setting up a custom print service to take advantage, also seems to be hidden behind a high level admin profile.
Ok, do you know where I can find a tutorial on how to do this from arcgis pro to agol?
I'll check. Some of these things can be published from Pro to a portal.
Let me see if I can find that link...
HEre are a couple that may be relevant
Configure utility services
This one appears more aimed at Enterprise though:
https://enterprise.arcgis.com/en/server/latest/publish-services/windows/tutorial-publish-additional-...
Note, that in theory you can go login to a portal (enterprise or agol) go to New and in the box to drag and drop, drag a layout you created and saved out of pro onto it, give it a name, tags, etc.
Ok, but what I don't get is how to use it after in experience builder as a widget or tool. Do you know that part ?
There is a default print widget, if you get the print utility into your experience, from the gear icon I think it is. Then in your print widget you can set it up, and the templates there should appear after saving and preview/publishing it.
from the print widget... you can configure the tasks.
The key I believe is the ExportWebMap Task
On the printing on the custom widget side, I don't have that fully answered yet.