As content and dependencies are cloned, Admin Tools prevents duplicates by looking for items in the target that share the same EXACT title and owner. If the tools find them, the cloning logic will attempt to wire the dependencies to it.
While this both necessary for the cloning operation , and is ( to prevent moving a layer or map multiple times if it is referenced by multiple parent items), it is also intended to save time, this same logic should be taken into consideration when moving content to a target that has pre-existing items prior to cloning. . Time can be saved using this by moving larger services in small groups BEFORE moving webmaps that rely on the services.
| Info |
|---|
|
If you want to save time by manually standing up your feature services or map services, the cloning logic will allow for this. |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | GJKBASE |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ("title","items","clone","owner","cloning") and type = "page" and space = "GJKBASE" |
|---|
| labels | Clone Cloning Items Title Owner |
|---|
|
...