...

These class names must be used as they will be recognized and mapped to corresponding fi2 object types.

Here is a sample with mappings for Fi2 classes (note, that internal class names may vary in your system).

...

Map Data fields

For each class, user can define any number of mapped fields. 

• Source class: External class from fi2 schema

• Source field - External field name, used when exporting to generic type

• Target field - Internal Field

• Source field type (Fi2 Field Type) - External field type, e.g. area, class etc

• Source value type (Fi 2 Value Type) - External sub type, e.g. BRA, NTATarget field - Internal Field

Sample usage of fields mapping for Fi2 and Space object:

...

As an example, in this mapping first row we are instructing the system to export our space_bra field as AREA tag with fi2area_code set to BRA.

Please inspect the specific types listed below and their possible values for “Value Type” and their impact on the output XML.

Possible field types

Source field type - Fi2 Field Type

• AREA - use for fields containing area values. Requires Source value type

• CLASS - use with dictioranry dictionary / lookup fields

• VALUE - use for generic values

• ID - use for object ID values

• NAME - use fro from object name tag

• ADDRESS - use for object address tag

• DESCR - use for object description tag

• CONSTRYEAR - use for object contrition year tag

...

<fi2struct_constryear>2014-03-12T11:53:03.100</fi2struct_constryear>

ADDRESS sample

<fi2struct_address></fi2struct<fi2prop_address>
   <fi2addr_addrline>SIMRISBANVÄGEN 14</fi2addr_addrline>
</fi2prop_address>

Possible Value Types

...

Source value type

• BRA

• NTA

• BTA

• class url

• etc

ADDRESS Value Types

Address supports specific value types: