Skenarios support
Import properties
Import buildings
When importing buildings, it is mandatory to provide the following information:
A unique building ID
Location data: This can be provided in one of the following ways:
Latitude and Longitude (coordinates)
A full address (country code, postcode, street address, and city)
A National Building ID
Additionally, you can provide further details about a building using optional headers.
To calculate renovations, you should include the building floor area, year, prototype, number of floors, and location details.
Mandatory Headers
Column title | Description | Allowed values |
---|---|---|
Building id AND | An organization level unique building id. | Unique string |
Latitude and longitude OR | Make a column for latitude and a column for longitude. The coordinates are to be inside the building. | Numeric |
National building id OR | Specifies the unit in a building. The full address of the building is required when using the Unit specifier without Unit id. Unit specifier value can be anything which is unique within the given address. | Any string |
Country code, postcode, street address and city | Make a column for each of the four titles. Country code can take values FI, CA, CH, PL, SE, PT, UK, US, BE. | String |
Optional headers
Column title | Description | Allowed values |
---|---|---|
Building name | Name of the property building. If you have provided any other mandatory fields, it will be created automatically for you. | Any String |
Group id | Used to identify which group this property belongs to. If this is not given, it'll be created automatically. Should be unique within the organization. | Any string |
Group name | Name of the property group. If this is not given, it'll be created automatically for you. | Any string |
Building prototype | Usage type of the property building. If building year will be empty, building prototype will be ignored. |
|
Electricity energy type | electricity, solar pv | |
Heating energy type | electricity, undefined heating system, district heating, air to air heat pump, air to water heat pump, exhaust air heat pump, water source heat pump, ground source heat pump, gas boiler, gas condensing boiler, oil boiler, solid fossil fuel boiler, wood pellet boiler, wood chip boiler, fireplace, solar collector, fireplace, solar collector | |
Building floor area | Gross floor area of the building in m2. (FI: Bruttoala) | Integer |
Building net internal area | Net indoor area of the building in m2. (FI: Huoneistoala) | Numeric |
Building gross internal area | Gross indoor area of the building in m2. (FI: Kerrosala) | Numeric |
Floors | Amount of levels in the building. Ground floors is counted as one. | Integer |
Floor height | (Average) floor height in the building in metres. | Integer |
Build year | Build year of the building. Mandatory field for building prototype. | Integer |
Building volume | The volume of a building in m3. | Integer |
Facade | The facade material of the building. | brick, concrete, metal, plaster, wood |
Roof | The roof material of the building | bitumen, metal, tile |
Car parking | Type of car parking | None, Parking space, Garage, Carport, Undercover parking |
Lot size in m2 | Lot size in m2 | Numeric |
Own lot | Own lot | Boolean |
Is waterside lot | Is waterside lot | Boolean |
End year of lot lease | End year of lot lease | Numeric |
Garden building(s) | Garden building(s) | Boolean |
Is housing company | Is housing company | Boolean |
Property image URL | Property image URL | Text |
Technical Value | Building technical value for given year | Numeric |
Repurchase Value | Repurchase value for given year | Numeric |
Building condition | Building condition (%), if Repurchase value is not set, this value will be used for Repurchase value calculation, otherwise a default one will be used | Numeric |
Condition Year | Condition year. Must be set if one of three values above are being imported | Integer |
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 |
Import custom attributes
It is possible to import values for the building's custom attribute value fields such as property image. Prior to a custom field import, however, it is mandatory to create the field for a portfolio. For more information about creating a custom field, please refer to the Settings page.
To import value for the custom property field, enter the title of the property field as a header to the Excel sheet as it would be any normal field. If there are multiple fields with the same title, first field will be used, but it remains undecided, which one.
Import Units
Certain headers are mandatory in order to import a unit, but additional details can also be imported by optional headers.
Mandatory Headers
A unit id is mandatory in order to import a unit. A unit id has to be unique in a portfolio. In addition, units are required to be linked to a building or a group (or both) by a building id or a group id.
Column title | Description | Allowed values |
---|---|---|
Unit id | Specifies the unit in a portfolio. If this is not given, it'll be created automatically. Must be unique on organization level. | Any string |
Building id OR | The id of the building where the unit is located | Any string |
Group id OR | The id of the property group where the unit is located | Any string |
Optional headers
Column title | Description | Allowed values |
---|---|---|
Unit name | Name of the property unit. If this is not given, it'll be created automatically. | Any string |
Unit description | Free text field for the description of the unit. Also, all information under the headers in your file that are not listed in these instructions will be presented here. NOTE: rows, where the header is misspelt will appear here. | Any string |
Unit price | Property units total value in local currency. Current date will be used as the value date. | Integer |
Total floor area | Unit's total floor area in m2. | Integer |
Unit Habitable Floor Area | Unit habitable floor area in m2 | Integer |
Unit usage type | Type of usage purpose of the unit. Allowed values are: Residential, Office, Retail, Storage or Other | String |
Unit floor | Unit's floor. Number 1 being ground floor. | Integer |
Condition | Unit's condition | Excellent, New, Good, Mediocre, Poor |
Number of rooms | Number of rooms | Integer |
Sauna | Type of sauna. Only for residential units in Finland. | Yes, No, Sauna building, Lakeside sauna |
Type of Balcony | Type of balcony | Yes, No, Glazed Balcony, French Balcony |
Type of Kitchen | Type of kitchen | Kitchen, Open Plan Kitchen, Kitchenette |
Type of Terrace | Type of terrace | Yes, No, Glazed Terrace |
Has fireplace | Has fireplace | Boolean |
Monthly Maintenance Fee | Monthly maintenance fee | Integer |
Monthly Housing Loan Fee | Monthly housing fee | Integer |
Mortgage Application Id | Mortgage application Id | 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 |
Import custom attributes
It is possible to import values for the unit's custom attributes value fields such as property image. Prior to a custom field import, however, it is mandatory to create the field for a portfolio. For more information about creating a custom field, please refer to the Settings page.
To import value for the custom property field, enter the title of the property field as a header to the Excel sheet as it would be any normal field. If there are multiple fields with the same title, the first field will be used, but it remains undecided, which one.
SkenarioLabs