A maintenance i Maintenance is subject to a property unit and it is highly recommended that maintenances are imported the property unit, building and group. When importing maintenance, remember to include them in a separate sheet, where they are tied to a unit, building or group by the corresponding ID. Certain headers are mandatory in order to import a maintenance, but additional details can also be imported by optional headers.
If a unit IDproperty id, date, and type are imported via Excel, but the corresponding values are already in the database, the existing maintenance is updated.
There can be only one maintenance per type per day (f.ex. you can’t have “Administration 2023-01-01” maintenance for the same property twice) when updated with Excel import. This will not cause error right now, but SkenarioLabs team is looking into issue!
Mandatory headers
Column title | Description | Allowed values |
---|---|---|
Entity ID | An entity ID of the corresponding entity type subject to the maintenance | String |
Entity Type | Type of entity | PROPERTY_UNIT, PROPERTY_BUILDING, PROPERTY_GROUP |
Maintenance cost | Cost of the maintenance | Number |
Maintenance date | Date of a maintenance | Date |
Maintenance type | Type of maintenance |
|
Attempting to import a maintenance with an incompatible part will raise an error and the row will not be saved in the databasesystem.
Optional headers
Column title | Description | Allowed values |
---|---|---|
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 |