A maintenance i subject to a property unit and it is highly recommended that maintenances are imported in a separate sheet, where they are tied to a unit by the corresponding ID. Certain headers are mandatory in order to import a maintenance, but additional details can also be imported by optional headers.
...
| Column title | Description | Allowed values |
|---|---|---|
| Unit Entity ID | A unit An entity ID of the unit corresponding entity type subject to the lease contractmaintenance | StringUnit maintenance |
| Entity Type | Type of entity | PROPERTY_UNIT, PROPERTY_BUILDING, PROPERTY_GROUP |
| Maintenance cost | Cost of the maintenance | Number |
| Unit maintenance Maintenance date | Date of a maintenance | Date |
| Unit maintenance Maintenance type | Type of maintenance | Administration, Balcony, Bathroom, Bricklaying, Carpenter, Chimneys, Cleaning, Doors, Drainage & Groundworks, Electrician, Electricity bill, External wall, Fitter/Cleaner/Handyman/PlastererRepairs, Floorer, Gas & Heating, Glazier, Heating bill, Insurance, Interiors, Lift, Management charge, Misc, Operation and maintenance, Outdoor maintenance, Plumber, Property tax, Rent, Repairs, Roofer, Safety & Security, Sitework, Waste manangementmanagement, Water and wastewater. |
* Attempting to import a maintenance with an incompatible part will raise an error and the row will not be saved in the database.
...
| Column title | Description | Allowed values |
|---|---|---|
| Unit maintenance Maintenance description | Free description | String |
Portfolio id | The id of the portfolio where the building should be imported. If the portfolio id is set Organization key header became mandatory otherwise row will be skipped. The portfolio id should exist within the organization used as organization key and user should be a part of the organization too otherwise row will be skipped. | Integer |
Organization key | The key of the organization where the building should be imported. If the Organization key is set Portfolio id header became mandatory otherwise row will be skipped. The Organization key should exist as parent/child organization and user should be a part of the organization too otherwise row will be skipped. | Text |