![]() ![]() This function supports all simple data items including file geodatabases, shapefiles, code samples, Pro project packages, etc. Clone content more efficiently with the API method clone_items(). These items will copy over just fine, but will continue to point back to the original source URL. Roles, users, and groups must be copied over first, because content must be owned by users, and have to be shared to groups.Ĭertain content items will not clone well, including map services and image services. Next copy over the groups from the source portal. The process will copy custom roles, users, groups, and items.īegin by copying any custom user roles (viewer, data editor, data scientist, etc.), and assign all the same user privileges. ![]() Getting started with cloning between portalsįirst, let’s establish a connection with the source portal, followed by connecting with a target portal where all the items, groups, and content will be copied over to. Cloning doesn’t work well for built-in user accounts, hosted tile services, map services, image services, and for complicated story maps. Cloning works best for web-based authenticated users, groups and sharing, hosted feature services, web apps based on web app templates or Web AppBuilder, and hosted feature layer views. This includes transfer from ArcGIS Enterprise to ArcGIS Online, Enterprise to Enterprise, or Enterprise to ArcGIS Online. Leverage the Python API to clone content from one portal to another. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |