Document toolboxDocument toolbox

Support center for flex.bi version 3.2

Account parameters for Private server

Owned by Edijs Vilciņš
Last updated: Sept 20, 2016 by Laima (Deactivated)
3 min read

What is  "account parameter"  and how to use it ?

When making a new account it is possible to add different account options - called account parameters.

  • Plan parameters  - To validate subscription plans and filtering by object, item, customer classes 
  • Data import parameters  - Specify the amount of parallel SQL threads during data import and  select or deselect Not Oked records.

  • Features parameters  - Adds some specific functionality or MDX hardcoded measures
     
     

    Please Note

    Add in the parameters textbox when making a new customer account.


     Parameters can be added only when making a new account otherwise, data for the account should be re-imported (in case of account upgrade or etc.)


Plan parameters

 If no account plan is selected with parameter, "start"  will be selected as default. Those parameters automatically will enable Dynamic Dimensions as Object Types, Item and Customer classifications options according to plan.

 

Assign parameters to predefined flex.bi plan packages:

 

[hansaworld]
flexbi_plan = "start" 

 

 There are 3 predefined packages at the moment:

  • "start "- enables the sales cube, the financials cube, the sales order cube and the quotations cube
  • "standard"  - enables everything in the start plan and additionally enables the stock cube and adds support for item classes, customer classes, objects
  • "business" - enables everything in the standard plan and additionally enables the CRM and the Job Costing cube


Data import parameters

 

Set up profit account to be ignored when importing transactions

 

[hansaworld]
profit_account = 31100

 

Set this to true to also import not OKed invoices

 

[hansaworld]
import_not_ok_invoices = true

 

Set this to true to also import not OKed Sales Orders

 

[hansaworld]
import_not_ok_sales_orders = true

 

Set this to true to also import not OKed Goods Receipts

 

[hansaworld]
import_not_ok_goods_receipts = true

 

Specify the amount of parallel SQL threads during data import

 

[hansaworld]
import_thread_count = 3

 

The parameter import_thread_count = 3 will import activities, invoices and transactions in 3 parallel SQL threads which should roughly double the speed of import. 
Setting import_thread_count = 1 will import at the default speed.
Setting import_thread_count = 3 will reduce the import time by roughly 10%.
Setting import_thread_count = 4 will reduce the import time by roughly 20%.

 

 

[hansaworld]
consolidated_companies = [1, 2, 3]

 

Adding this parameter will enable the the Companies dimension which will allow you to then import TRVc files for specific companies only. For example a file named 1_TRVc.txt will import the entirety of the file for company 1 that is described in the CompaniesBlock file. Any other TRVc file that does not have a number in front of it that can also be found in the consolidated_companies parameter will be ignored.

 

Specify refresh period in days (new in version 3.1). 

A refresh_period_in_days parameter allows you to enter the amount of days from the registers last import date from which to import data. 
Example: Invoices were imported on 2016-09-16. refresh_period_in_days = 10. The next import will import everything from 2016-09-06.

[hansaworld]
refresh_period_in_days = 10

If start date is given and refresh_period_in_days exceeds the start date, it will not override the start date - the application will import everything from start date.

Example: Set start date from month ago and refresh_period_in_days = 60, application will import only one month.

If start date is not given, application imports last one year by default. If refresh_period_in_days parameter exceeds one year, it overrides the default.

Example: No start date given and refresh_period_in_days = 600, application will import last 600 days, not only the default last one year.

Features parameters

Enable loyal / active / new customer etc. features 

 

[hansaworld]
update_active_customers = true
update_loyal_customers = true
update_new_customers = true

Available options

  • update_active_customers - import row counts active clients. True/false option which will be availible in the propertyCustomers dimension. Example:

     

    Count(Filter([Customer].[Customer].Members, [Customer].getBoolean('Active')))

  • update_loyal_customers - at the time of import loyal clients will be counted. It will become a true/false option and after thet availible in the propertyCustomers dimension. (A loyal customer has at least 3 invoices in the last 6 months, but not in the same month) Example:

     

    Count(Filter([Customer].[Customer].Members, [Customer].getBoolean('Loyal')))

  •  

On this page