Advanced Settings for Custom Field import

Advanced settings - Step by Step

With Advanced settings for Custom Fields functionality you can:

1) create new data structures :

Add New Dimensions
Add new Properties
Add new Measures
Add new Hierarchies
Add new Data cubes (See Example HERE)

2) define custom views and advanced sharing

Share measures between data cubes
Define Custom Drill Options

What is a considered as a "custom field" for flex.bi ?

field in Source system that is not imported in flex.bi by default
For example : Custom Field that is customer specific

transaction Register Field in Source system that is not imported in flex.bi by default,
For example : Custom Module that is customer specific and is based on customer register
any addition data structure that exists in Source system that needs be used in flex.bi as dimension/ Measures or property etc. in reports

Where to find Advanced settings ?
Advanced settings is a section in flex.bi applications that allow you to define custom data input for flex.bi data cubes, create new data cubes and adjust them.

How to use this function?

STEP 1

Define what you want to add in “Advanced settings” sectioning XXX language.
Custom field Code has to be described in blocks and organised based on type

STEP 2

Select in Cube Properties section — Custom Fields section what you want to import and how.

Watch a Demonstration here :

Advanced setting key components & detailed instructions for Standard ERP

Below is a description of necessary parameters to define simple custom fields and a description of the process by steps.

1. Find the field name

First, you need to find out the register and REST API code for the field. You can find codes for registers in the HansaWorld source File import documentation page. Then you can use the code to find code for REST API field in HansaWorld Module Technics → Reports → Import/Export format.

You can see in the example screenshot below the register code (1.) and codes for REST API fields (2.).

2. Configure custom field settings

Register code and register REST API code

CODE

[register_code.register_rest_api_code]

Where register_code is register code and register_rest_api_code is the register REST API code. This will start the block of configuration parameters for the custom field.

Name for the custom field

A name for the field describing the logic in the most understandable for you way e.g.

CODE

name = "Price"

Cube Name

The cube name where the custom field will be available. You can find the full cube names in Analyze section in your flex.bi or if you would like to create a new cube you can use define the name here.

CODE

cube_name = "HansaWorld Invoices"

Dimension name in flex.bi for the register

Name of the dimension that should be created.

CODE

dimension_name = "Invoice"

Dimension level name

The name of the level within the specified dimension.

CODE

level_name = "Invoice Item"

Dimension item level names for registers that do not have dimensions: "Transaction Item", "Simulation Item".

Data type of this field

One of the supported data types - integer, value, string e.g.

CODE

data_type = "string"

By default, the string maximum length is 255 characters. If there is a need to import longer string values, then use the additional limit setting to specify the maximum length.
Other available types are text, integer, decimal, date, datetime.

If you use the decimal data type, then by default the precision (maximum number of digits) is 15 and the scale (digits after the decimal point) is 2. You can change these defaults with the additional precision and scale settings.

When defining fields for key_field, name_field, bind_field flex.bi will recognise that they will be strings and this parameter can be skipped.

Additional options

If you would like to import custom field as additional dimension then add

CODE

dimension = true

If you would like to import custom field as a measure then add

CODE

measure = true

If you would like to do operation with the incoming data before fields are imported you can use custom javascript code

CODE

javascript_code ='''
  if (doc.rows) {
    doc.rows.forEach(function(row){
    row.negative_rowGP = String(Number(row.rowGP) * -1);
  })
}
'''

If you would like to share the added measure to another cube then specify the cube name with the cubes_for_measure_sharing parameter:

CODE

cubes_for_measure_sharing = ["HansaWorld Invoices"]

If you are importing HansaWorld's data with files then the number of the field also needs to be defined. You can find what number is each field in your HansaWorld's "Technics → Reports → Export/import format" by specifying the register's code that you are importing.

CODE

file_field = 4

If an REST API field contains a full stop characters (“.“) or the same REST API should be used twice you can use rest_api_field to define the REST API field name instead. If rest_api_field is used then in order to change the returned value for the whole custom field using Javascript the name in rest_api_field needs to be referenced instead as well.

CODE

rest_api_field = 'T.NAME'

Example of custom dimension definition

CODE

[ORVc.LangCode]
name = "Language code"
cube_name = "HansaWorld Sales Orders"
data_type = "string"
dimension_name = "Sales Order"
level_name = "Sales Order"
dimension = true

Example of custom measure definition with javascript that imports the row gross profit but turns the numbers negative:

CODE

[QTVc.negative_rowGP]
name = "Quotation negative GP"
cube_name = "HansaWorld Quotations"
data_type = "decimal"
rest_api_item_field = "rows"
measure = true
javascript_code ='''
if (doc.rows) {
  doc.rows.forEach(function(row){
    row.negative_rowGP = String(Number(row.rowGP) * -1);
  })
}
'''

If the data need to be linked to another date field then use custom_date_measure_group to define the name for the measure group and also the prefix for the duplicated measures.

CODE

custom_date_measure_group = 'Planned'

Example for both record and item level below.

CODE

[SHVc.Planned_Send_date]
rest_api_field = 'PlanSendDate'
name = 'Planned Send Date'
dimension_name = 'Delivery'
cube_name = 'HansaWorld Deliveries'
custom_date_measure_group = 'Planned'

[SHVc.Plan_Send_DateRow]
name = 'Item Planned send Date'
dimension_name = 'Delivery'
level_name = 'Delivery Item'
cube_name = 'HansaWorld Deliveries'
custom_date_measure_group = 'Planned'
javascript_code ='''
  if (doc.rows && doc.PlanSendDate) {
    doc.rows.forEach(function(row){
      row.Plan_Send_DateRow = doc.PlanSendDate;
    })
  }
'''

Add additional custom field definitions as needed in advanced settings text area field and then click Save.

3. Import the custom field

Finally, Edit the HansaWorld source application again and in "Cube properties" section select your new defined custom field for import.

Save the application settings and start the import. After the import is finished start using your property, measure or dimension in your reports.

In case of any questions please contact support@flex.bi for more information.

Defining dimension in a separate table

If you would like to have a dimension definition that has a hierarchy, has a key and name separately or you would like to add additional properties to the dimension then you can use a more advanced definition. The definition consists of 3 parts:

A field that contains the keys for dimension elements
A field that contains the name for dimension elements (optional)
A field that binds the dimension to measures

Key field

Using the custom field definition and an additional parameter key_field you can define that this field will be used as a key for the new dimension.

CODE

[INVc.item_code]
name = 'Item Code'
dimension_name = 'Item2'
cube_name = "HansaWorld Invoices"
rest_api_field = "Code"
key_field = true

Name field

Using the custom field definition and an additional parameter name_field you can define that this field will be used as a name for the new dimension.

CODE

[INVc.item_name]
name = 'Item Name'
dimension_name = 'Item2'
cube_name = "HansaWorld Invoices"
name_field = true
rest_api_field = "Name"

Bind field

While the dimension members will be imported with the key_field and name_field definitions a bind field also needs to be defined so that flex.bi can know what field from the register where measures is imported will be linked to this new dimension. For this 2 parameters have to be used: bind_field_name and for_custom_dimension.

bind_field_name is the field's rest api code that we defined previously (the "item_code" from this "[INVc.item_code]") and the for_custom_dimension is the name of the dimension we want to link the measures import to.

If the bind field from the measures import register is available only on the item/row level rest_api_item_field parameter can be used to specify this.

CODE

[IVVc.item_code_bind]
name = 'Item Code bind'
cube_name = "HansaWorld Invoices"
for_custom_dimension = 'Item2'
rest_api_item_field = "rows"
bind_field_name = 'item_code'
rest_api_field = 'ArtCode'

Consolidation

When consolidation is enabled for an account (with parameter max_consolidated_companies) all registers will have 2 more fields available when defining custom fields - source_company_code and source_company_name. During data import these fields will contain code and name that represents the company that the data is imported from and can be used to create a Company dimension and additional hierarchies for all the dimensions.

The example below shows what fields would need to be added to create another “Company” hierarchy level in “Sales Person” dimension. For Horizon application both rest_api_field and skip_request = true parameters have to be used at the same time.

CODE

[TNdmPardSar.p_company_code]
default_custom_field = true
cube_name = 'Horizon Invoices'
dimension_name = 'Sales Person'
level_name = "Company"
name = 'Person company code'
rest_api_field = "source_company_code"
skip_request = true
key_field = true

[TNdmPardSar.p_company_name]
default_custom_field = true
cube_name = 'Horizon Invoices'
dimension_name = 'Sales Person'
level_name = "Company"
name = 'Person company name'
rest_api_field = "source_company_name"
skip_request = true
name_field = true

[TNpvzRndAllSar.sales_person_company_bind]
default_custom_field = true
cube_name = 'Horizon Invoices'
name = 'Sales Person Company Bind'
skip_request = true
rest_api_field = 'source_company_code'
for_custom_dimension = 'Sales Person'
for_custom_dimension_level = 'Company'
bind_field_name = 'p_company_code'

Available parameters for Advanced Settings

Below you can find a list of all the available custom field parameters.

Parameter Name	Example	Description
default_custom_field	default_custom_field = true	This parameter specifies that this field is loaded from the default custom fields file and is required for building the standard cube structure. A custom field with this parameter enabled can't be de-selected for import. Also, if this parameter is set, then the custom field definition is not validated.
key_field	key_field = true	This parameter specifies that this field will be used as the key field for binding the dimension to the measures and as the first part of dimension member's name ("`key_field` - `name_field`").
name_field	name_field = true	This parameter specifies that this field will be used as the second part of dimension member's name ("`key_field` - `name_field`").
level_name	level_name = "Invoice Item"	If a dimension has multiple levels `level_name` parameter should be used to specify the level. This parameter should not be used with dimensions that have only 1 level.
source_id_field	source_id_field = true	This parameter specifies that this field should be used for binding the dimension to the measures instead of the key field. For example, when importing data from a relational database, this could be the primary key of the table that is used for dimension creation.
rest_api_field	rest_api_field = 'T.NAME'	If an REST API field contains a full stop characters (“.“) or the same REST API should be used twice you can use rest_api_field to define the REST API field name instead. If rest_api_field is used then in order to change the returned value for the whole custom field using Javascript the name in rest_api_field needs to be referenced instead as well.
for_custom_dimension	for_custom_dimension = 'Customer'	This parameter specifies that this field from the measures register or table will be used for binding the measures to the particular dimension. This parameter should be used together with the following parameters, to specify the particular use of the custom field: `key_field, name_field, source_id_field`.
for_custom_dimension_level	for_custom_dimension_level = 'Customer'	This field is an addition to `for_custom_dimension` field and can be used to also specify a level for binding measures to the particular dimension.
import_sort_date	import_sort_date = true	This parameter specifies that this field will be used for limiting data requests from the particular register or table. For instance, it will be used to get data starting from a particular start date, to rewrite data for a specified refresh period and also for incremental import of only those data lines that have been changed since the last import run.
skip_request	skip_request = true	This parameter specifies that the REST API request should be skipped for this field. This can be useful when the field has been already requested in another custom field or the field is calculated with Javascript.
bind_field_name	bind_field_name = 'status_code'	This parameter specifies what custom field's register code should be used for binding measures to another dimension. With this parameter the same field can be referenced multiple times.
matrix_field	matrix_field = true	This parameter specifies that the information should be taken from matrix level of a record for creating a dimension.
ordinal_field	ordinal_field = true	This parameter specifies that the field should be used as an ordinal column for dimensions in a separate table.
credit_debit_dimension_column	credit_debit_dimension_column = true	This parameter specifies that the values for the particular custom field should be taken from 2 separate custom fields with name prefixed `credit_` and `debit_`. Works only for specific cubes (Jumis Financials, Horizon Financials).
for_standard_dimension	for_standard_dimension = "Customer"	Similar to `for_custom_dimension` this parameter specifies that this field from the measures register or table will be used for binding the measures to the particular dimension with the difference that this parameters should be used for already standard existing dimensions that have been defined without custom fields.
for_standard_dimension_level	for_standard_dimension_level = "Customer"	Similar to `for_custom_dimension` parameter and can be used to also specify a level for binding measures to the particular dimension with the difference that this parameters should be used for already standard existing dimensions that have been defined without custom fields. This is optional if the data is linked to the lowest hierarchy level.
property_with_mdx	property_with_mdx = true	Automatically creates a calculated measure for the imported property.
drill_through_return	drill_through_return = true	drill_through_return parameter can be used to specify that the dimension should be included in the result as a column when "Drill through cell" is used on a cell.
drill_through_default_measure	drill_through_default_measure = true	`drill_through_default_measure` parameter can be used to specify that the measure should be included in the result as a column when "Drill through cell" is used on a cell with a value from a calculated member.
drill_through_dimension_level	drill_through_dimension_level = true	`drill_through_dimension_level` parameter can be used to specify that the dimension will be available in the selection when using "Drill through" option on a cell.
default_measure	default_measure = true	`default_measure` parameter can be used to specify that the measure should be enabled by default when a new, empty report is created.
rest_api_item_field	rest_api_item_field = "TRANSORDER_P"	This field can be used to specify how to reference item level from a record correctly. Using this field once is sufficient as this will overwrite the item level name reference from request for the same dimension for other custom fields as well.
rest_api_nested_field	rest_api_nested_field = "SHIPTO2"	This parameter can be used to specify a record sub-level that's field will be requested through the REST API for the register, and available for custom field definition on the record level. If the sub-level is an array then the first element from the array will be used.
request_filter	request_filter = 'NDOK.D.T.KODS+eq+RREK'	This parameter can be used to add additional filters to the REST API link when requesting data. Currently only supported for Horizon application.
item_level_from_header_key	item_level_from_header_key = 'NDOK_PK_DOK'	This parameter can be used as a key value to create the item level from the header level data. The key is used as the unique identifier for aggregating item level rows that belong to the same record. Currently only supported for Horizon application.
cubes_for_measure_sharing	cubes_for_measure_sharing = ["HansaWorld Invoices", "HansaWorld Sales Orders"]	When defining a new custom field this field can be used to specify in what other cubes this measures should be shared in.
source_cube_name	source_cube_name = 'HansaWorld Sales Orders'	Can be used to share measures from standard HansaWorld data cubes to other cubes. This parameter specifies from what cube the measure comes from. Should be used together with "source_measure_name".
source_measure_name	source_measure_name = "Item base amount"	Can be used to share measures from standard HansaWorld data cubes to other cubes. This parameter specifies the name for the measure that should be shared. Should be used together with "source_cube_name".
display_name	display_name = "URL"	This parameter can be used alongside "name" property to specify the property or measure name displayed in the data cube. This can be useful when the same field name has to be used multiple times (otherwise there would be an error that the same name can't be used twice).
custom_date_measure_group	custom_date_measure_group = "Planned"	This parameter can be used to duplicate measures for HansaWorld application and link the duplicated measures to a different time period. The type for the custom field with this parameter has to be a date. This parameter also groups the duplicated measures with the name specified.
query_params	query_params = 'DATUMS=today+1.day'	Can be used to add additional parameters for the Rest API request. The parameter values are specific to the source application. The example is for Horizon application and allows to pass a dynamic date value to the Rest API request. This parameter is specified for a single register in the custom fields definition.
empty_before_import	empty_before_import = true	Allows to specify that a particular register data should be deleted before each import operation. This parameter is specified for a single register in the custom fields definition.
model	model = 'hr.employee'	This parameter is specific for Odoo application. It allows to set the Odoo API model name for a particular register import. This can be specified only once per register in custom fields definition.
dimension_bind_field_name	dimension_bind_field_name = 'classificator_id'	Can be used to import additional data (property values) for a custom dimension, using another register as a source. For instance, you can create a Customer dimension from Register1 and then add Customer Classification values from Register2, using `dimension_bind_field_name` as a reference value for the import. See example below.
import_order	import_order = 1	Can be used to specify import order of custom cubes. This parameter should be specified in any measure custom field definition for a particular cube. If no parameter is specified, the cube is imported last.

Creating custom dimension from multiple registers

In the following example, a custom dimension Employee is created from two registers in Odoo application. The main dimension structure, including key fields, is created from the employees register, but the Employee Category value is imported from the categories register, using the category_id field as a key for binding the categorie values to the relevant employee record.

CODE

#===========Employee Dimension (main) in Odoo Timesheets Cube================
[employees.employee_id]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Employee Id'
rest_api_field = 'id'
key_field = true
model = 'hr.employee'
query_params = [['active', 'in', [true, false]]]

[employees.name]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Employee Name'
name_field = true

[employees.active]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Employee Status'
property = true
javascript_code = '''
switch(doc.active) {
  case true:
    doc.active =  "Active";
    break;
  case false:
    doc.active =  "Inactive";
    break; }
'''

[employees.category_id]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Employee Category Id'
rest_api_field = 'category_ids'
property = true

#===========Employee Dimension (additional) in Odoo Timesheets Cube================
[categories.category_id_bind]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Category Id Bind'
rest_api_field = 'id'
dimension_bind_field_name = 'category_id'
model = 'hr.employee.category'

[categories.category]
default_custom_field = true
cube_name = 'Odoo Timesheets'
dimension_name = 'Employee'
name = 'Employee Category'
property_with_mdx = true
rest_api_field = 'name'

Skipping and deleting records

If it's necessary to skip or delete records during import, define a custom field "delete_and_skip". All the records that will have "true" value for this custom field will be skipped and also deleted if they have have been already imported. Example below.

CODE

[TdmGramatSL.delete_and_skip]
default_custom_field = true
name = 'Delete and Skip'
dimension_name = 'Transaction'
cube_name = 'Horizon Financials'
skip_request = true
property = true
javascript_code = '''
  switch(doc.STATUSS) {
    case "1":
      break;
    default:
      doc.delete_and_skip = 'true';
    }
'''

Advanced Settings examples

In the example below, a combination of Price List, Price and Customer registers are used to create 3 level hierarchy.

CODE

[PLVc.F_PriceList]
name = 'Price List Code'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Price list'
rest_api_field = "PLCode"
key_field = true

[PLVc.F_PriceListName]
name = 'Price List Name'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Price list'
rest_api_field = "PLCode"
name_field = true

[PLVc.F_PriceItemCode]
name = 'Price Item Code'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Item'
rest_api_field = "ArtCode"
key_field = true

[PLVc.F_PriceItemName]
name = 'Price Item Name'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Item'
rest_api_field = "Comment"
name_field = true

[PLVc.F_PriceCustomerCode]
name = 'Price Customer Code'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Customer'
rest_api_field = "CustCode"
key_field = true

[PLVc.F_PriceCustomerName]
name = 'Price Customer Name'
dimension_name = 'Price'
cube_name = 'Hansaworld Invoices'
level_name = 'Customer'
rest_api_field = "CustCode"
name_field = true

[IVVc.PriceListProperty]
name = "Price list Property"
cube_name = 'Hansaworld Invoices'
data_type = "string"
dimension_name = 'Invoice'
level_name = 'Invoice'
rest_api_field = 'PriceList'

[IVVc.RowPriceListCode]
name = 'Invoice Price List Code'
cube_name = 'Hansaworld Invoices'
for_custom_dimension = 'Price'
for_custom_dimension_level = 'Price list'
bind_field_name = 'F_PriceList'
rest_api_item_field = "rows"
javascript_code = '''
if (doc.rows) {
  doc.rows.forEach(function(row){
    if (doc.PriceList){
      row.RowPriceListCode = doc.PriceList;
    }
  })
}
'''

[IVVc.ArtCode]
name = 'Invoice Item Code'
cube_name = 'Hansaworld Invoices'
for_custom_dimension = 'Price'
for_custom_dimension_level = 'Item'
bind_field_name = 'F_PriceItemCode'
rest_api_item_field = "rows"

[IVVc.RowCustCode]
name = 'Invoice Customer Code'
cube_name = 'Hansaworld Invoices'
for_custom_dimension = 'Price'
for_custom_dimension_level = 'Customer'
bind_field_name = 'F_PriceCustomerCode'
rest_api_item_field = "rows"
javascript_code = '''
if (doc.rows) {
  doc.rows.forEach(function(row){
    if (doc.CustCode){
      row.RowCustCode = doc.CustCode;
    }
  })
}
'''

In the example below, account_code value will be populated from the credit_account_code for the credit transaction and from debit_account_code for debit transaction.

CODE

[FinancialDocLine.account_code]
skip_request = true
default_custom_field = true
name = 'Transaction Account Code'
dimension_name = 'Transaction'
cube_name = 'Jumis Financials'
for_custom_dimension = 'Account'
bind_field_name = 'account_code'
credit_debit_dimension_column = true

[FinancialDocLine.credit_account_code]
default_custom_field = true
name = 'Credit Account Code'
dimension_name = 'Transaction'
cube_name = 'Jumis Financials'
rest_api_field = 'CreditAccount.AccountCode'

[FinancialDocLine.debit_account_code]
default_custom_field = true
name = 'Debit Account Code'
dimension_name = 'Transaction'
cube_name = 'Jumis Financials'
rest_api_field = 'DebetAccount.AccountCode'

In the example below, a Customer dimension with two hierarchy levels Customer type and Customer is defined. This dimension contains both key and name fields for both levels and is linked to the measures (Transaction dimension) using customer_code key field. In this example, customer_name is defined both for Customer and Transaction dimension import. This allows for Customer dimension member creation from the Transaction record in case a matching customer code is not found in the Customer dimension.

CODE

[TdmGramatSL.customer_code]
default_custom_field = true
cube_name = 'Horizon Financials'
name = 'Transaction Customer Code'
rest_api_field = 'D.K.KODS'
for_custom_dimension = 'Customer'
bind_field_name = 'customer_code'

[TDdmKlBaseSar.customer_type_code]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Customer'
level_name = 'Customer Type'
name = 'Customer Type Code'
rest_api_field = 'K.KTIPS'
key_field = true

[TDdmKlBaseSar.customer_type_name]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Customer'
level_name = 'Customer Type'
name = 'Customer Type Name'
skip_request = true
name_field = true
javascript_code = '''
cust_type = doc.K_KTIPS;
switch(cust_type) {
  case "0":
    doc.customer_type_name =  "Active";
    break;
  case "1":
    doc.customer_type_name =  "Potential";
    break; }
'''

[TDdmKlBaseSar.customer_code]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Customer'
name = 'Customer Code'
rest_api_field = "K.KODS"
key_field = true

[TDdmKlBaseSar.customer_name]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Customer'
name = 'Customer Name'
rest_api_field = "K.NOSAUK"
name_field = true

[TDdmKlBaseSar.customer_pvn_reg_no]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Customer'
name = 'VAT Registration No'
rest_api_field = "K.PVN_REGNR"
property = true

In the example below custom fields are used to define an Account dimension with a Company hierarchy level at the bottom for consolidation.

CODE

[TdmAccEdList.account_type_code]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
level_name = 'Account Type'
name = 'Account Type Code'
skip_request = true
key_field = true
javascript_code = '''
acc_code = doc.KON_KODS;
if (acc_code) {
expense_regex = /(^82.*|^7.*|^8810|^8891)/;
income_regex = /(^81.*|^6.*)/;
doc.account_type_code = '3';
if (acc_code.match(expense_regex)) {
  doc.account_type_code = '2'
};
if (acc_code.match(income_regex)) {
  doc.account_type_code = '1'
};
}
'''

[TdmAccEdList.account_type_name]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
level_name = 'Account Type'
name = 'Account Type Name'
skip_request = true
name_field = true
javascript_code = '''
acc_type = doc.account_type_code;
switch(acc_type) {
  case '2':
    doc.account_type_name =  'Expense';
    break;
  case '1':
    doc.account_type_name =  'Income';
    break;
  case '3':
    doc.account_type_name =  'Other';
}
'''

[TdmAccEdList.account_code]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
name = 'Account Code'
rest_api_field = 'KON.KODS'
key_field = true

[TdmAccEdList.account_name]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
name = 'Account Name'
rest_api_field = 'KON.NOSAUK'
name_field = true

[TdmAccEdList.acc_company_code]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
level_name = "Company"
name = 'Account company code'
rest_api_field = "source_company_code"
skip_request = true
key_field = true

[TdmAccEdList.acc_company_name]
default_custom_field = true
cube_name = 'Horizon Financials'
dimension_name = 'Account'
level_name = "Company"
name = 'Account company name'
rest_api_field = "source_company_name"
skip_request = true
name_field = true