| Info | ||
|---|---|---|
| ||
With Advanced settings for Custom Fields functionality you can: 1) create new data structures :
2) define custom views and advanced sharing
What is a considered as a "custom field" for flex.bi ?
Where to find Advanced settings ? How to use this function? STEP 1 Define what you want to add in “Advanced settings” sectioning XXX language. STEP 2 Select in Cube Properties section — Custom Fields section what you want to import and how. |
Watch a Demonstration here :
Youtube macro width 300 aspectRatio 4 / 3 url https://www.youtube.com/watch?v=BOmOgM-TLV8 height 200
...
Advanced setting key components & detailed instructions for Standard ERP
...
| 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. |
| dimension_in_separate_table | dimension_in_separate_table = true | This parameter specifies that the particular dimension will be created in a separate table. However, when |
| 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: |
| 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_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. |
| item_level_from_header_key | item_level_from_header_key = 'NDOK_PK_DOK' | This parameter can be used to 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. |
Advanced Settings examples
...