> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloneable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up from your client file

> Build a Cloneable configuration from your SPIDAcalc client file and choose what fielders collect

A SPIDAcalc client file lists your poles, owners, anchors, parts and forms. Cloneable turns it into a configuration: the objects fielders collect, the fields on each, and the pick lists they choose from. You do this once per client file.

You need to be an **organization admin**.

## What gets mapped

| From your client file | In Cloneable |
| - | - |
| Poles (species, class, height) | A pole type pick list: species, then height, then class |
| Owners | A pole owner pick list, plus the client file's default owner |
| Anchors | An anchor type pick list on guy anchors |
| Environments | What each midspan is over |
| Wires, insulators, crossarms, equipment | The parts you pick from when you trace |
| Trusses, braces, bundles, foundations, wire-mounted equipment | Parts the tracer and export can use, when your file has them |
| Location forms | Fields on the pole, one per form field you choose |

## Build the configuration

Open **Settings** → **Configurations** → **New configuration** → **From a SPIDA catalog**. The builder walks you through six steps. Click **Next** to move on and **Back** to change an earlier step.

**1. Upload**

Drop your `.client` file on the page or click **Browse files** (up to 50 MB). Cloneable shows the catalog name, the **Client file version** and how many poles, owners, anchors, wires and location forms it found.

If Cloneable spotted anything unusual, a note says so. Click **Show the notes** to read them. Nothing there stops the build.

**2. Object types**

Choose what fielders collect: **Pole** (always included), **Span**, **Span measurement** (midspans) and **Guy anchor**. Turning on **Span measurement** also turns on **Span**. The relationships between them, such as each span linking two poles, are added for you.

**3. Fields**

Choose which fields each object collects. See [Choose what fielders collect](#choose-what-fielders-collect).

**4. Lists**

Choose which poles, owners, anchors and environments fielders can pick. Uncheck any you never want offered, or use **Select all** and **Clear all**. Keep at least one entry in each list.

The default owner from your client file shows here. Cloneable applies it on export when a pole has no owner; it isn't filled in on devices.

If your file has trusses, braces, bundles, foundations or wire-mounted equipment, they're listed too. Leave out any you don't want the tracer to offer.

**5. Review**

Type a **Configuration name**. The review shows the templates and fields, pick lists, defaults, and anything collected but not exported to SPIDAcalc.

Anything under **Fix before creating** must be fixed first. **Worth checking** items don't block you. Nothing is created until the next step.

**6. Create**

Click **Create configuration**. When you see **Configuration created**, click **Open configuration**.

> [!NOTE]
>
> If creating fails partway through, Cloneable removes what it made, so you can fix the problem and create again.

## Choose what fielders collect

The **Fields** step lists each object's fields in groups:

* **Always included**: what the export needs, such as location, measurements and the links between objects. You can't turn these off.
* **Optional attributes and catalog choices**: pole tag, pole type, owner, ground-line circumference, anchor type and the location details SPIDAcalc stores (remedies, comments, technician, address and so on). Some start on; extras like the location details and a typed pole height start off.
* **One group per location form**, named after the form. Pick the form fields your crews fill in.

Use the buttons at the top to jump to an object. Each shows how many optional fields are on, such as **Pole · 6/18 optional**.

> [!TIP]
>
> Only collect what your engineers use in SPIDAcalc. Every extra field is more typing in the field. You can change field defaults and conditional rules later in the configuration's templates.

## When your client file changes

To bring in new or changed parts from an updated client file:

1. Open the configuration and go to the **Pick list** step.
2. Click **Import SPIDA Client File** and choose the new file.
3. Save the configuration.

Parts you already used keep working, and new parts show up in the tracer and the export.

> [!WARNING]
>
> Re-importing updates parts only. It doesn't add new location forms or form fields, and it doesn't refresh the pole, owner, anchor or environment lists. For those, build a new configuration from the new file with a new name. Existing configurations and their jobs aren't changed.

## More than one client file

Build one configuration per client file. Each job uses one configuration, so pick the one that matches the client file your engineers will open the export with.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.