Skip to main content

​
Connecting

ArcGIS isn’t turned on for your organization yet. Contact Cloneable to turn it on. Once it’s on, an organization admin sees an ArcGIS tab under Settings → Organization.
ArcGIS rejected the connection’s sign-in, for example because the account’s password changed or access was revoked. An organization admin clicks Reconnect under Settings → Organization → ArcGIS. Nothing is written to ArcGIS with an expired sign-in.
Building a configuration needs a connected ArcGIS account. Ask an organization admin to connect ArcGIS.

​
Building a configuration

Cloneable can’t send to versioned data yet (ArcGIS Enterprise traditional or branch versioning). You can still build a configuration and import from it. To send results, use a non-versioned layer: choose Send to another layer when you send.
Polygons and multipoints aren’t brought in yet.
At least one field must be set to Crew in the Fields step.

​
Importing

A layer or column the configuration uses was removed or changed in ArcGIS. Click Build an updated configuration, then import again.
An import reads up to 20,000 features per layer. Narrow the area with Only features where and import the rest separately.
Two features in the layer share the same ID, so Cloneable can’t tell which one to use. Fix the duplicate in ArcGIS and import again.
The import keeps running on Cloneable’s servers. Open Import from ArcGIS again to see its progress.

​
Sending

Your organization writes each change as the person who made it, and that person hasn’t connected their ArcGIS account yet, or their sign-in expired. Only their features wait; everyone else’s are sent. Ask them to open the job on their phone and sign in to ArcGIS, or to click Connect your ArcGIS account under Settings → Account → ArcGIS. Then press Send again.If you’d rather have one account write everything, an admin can turn off ArcGIS: each person signs in under Settings → Organization → Features.
Ask your ArcGIS administrator to give that person edit access to the layer, then press Send again.
With individual sign-in, ArcGIS needs to know who made each change. These features have no Cloneable member recorded as making the change, so they’re held. Contact us if you see this.
The feature is missing something ArcGIS needs. Each reason names what to fix. Fix it in Cloneable, then send again.
The layer has no GlobalIDs, and Cloneable can’t find the feature it sent before. Sending again could add it twice, so it’s held. Check the feature in ArcGIS, and contact us if you need help.
ArcGIS asked Cloneable to slow down. Cloneable waits and tries again on its own. If it keeps happening, try again in a few minutes.
What was sent stays sent. An organization admin reconnects ArcGIS in Settings, then you send again. Only what’s left is sent.
Points and lines go to different layers. When you send to a point layer, spans and lines are counted separately and aren’t sent there.
The heights are drawn on measurement photos in your browser as you send. Any that couldn’t be drawn are sent next time.