# system.kanoa.tooling.saveToolType(typeInfo, userId)

Makes an asset type a tooling type, or not, and sets what a new tool of that type starts with. Tooling types are the ones the tool editor offers and the asset tree editor leaves out. Refused when making a type tooling that assets which aren't tools already have, that is a Mobile type, or that is a plant hierarchy level (enterprise, site, area, line, cell). Tools keep their type when it stops being a tooling type.

---

### Parameters

**typeInfo** `Dictionary`<br />
<table class='dictionaryKeyTable'>
 <tbody>
  <tr><td> - assetTypeId</td><td>Integer</td><td>Required</td></tr>
  <tr><td> - isTooling</td><td>Boolean</td><td>Required</td></tr>
  <tr><td> - hasPositions, holdsInserts, scalesOutput</td><td>Boolean</td><td>What a new tool of this type does. Default False</td></tr>
  <tr><td> - lifeUnit</td><td>String</td><td>'cycles', 'runMinutes' or 'calendarDays'</td></tr>
  <tr><td> - calibrationIntervalDays</td><td>Integer</td><td></td></tr>
 </tbody>
</table>

**userId** `Integer`: The user making the change<br />

---

### Returns

**(1, message)**<br />

---

### Example

```python
typeInfo = {'assetTypeId': 1, 'isTooling': True, 'lifeUnit': 'cycles', 'calibrationIntervalDays': 1}
userId = 5
result1, result2 = system.kanoa.tooling.saveToolType(typeInfo, userId)
```
