Best Of

Dear Abdul Malik,

please have a look to the attached link (Prerequisites): Board Server configuration 

Honestly the samples are just theoretical.

The real requirement depends to your database and concurrent working users.

As more concurrent users as more CPU you need.

As bigger your Database grows as more RAM you need.

For that reason perhaps it will make sense using virtual machine to be more flexible concerning scalability

hope it helps

regards

Alexander Kappes

Dear Annika Fava,

another option, but I don´t think that it is easier is calculating separate Cube just for the top 10 customers.

When you insert this plus the normal cube into your layout you just have to deduct the top10 from the normal cube and git the wished result.

But for that you have to run procedure, need a second cube and have to think for the best slot calculating your separate cube.

I think for all that constraints the nexel solution is the bette one.

Hope it helps

regards

Alexander Kappes

Dear Brady Knudsen,

thanks for your request.

Without any knowledge of your problem, another option without using 70 or more blocks can be using aggregation of your actual COA Hierarchy.

For example you can insert an aggregation entity for COA lets say COA Group.

Inside this you manage the relationships like the example shows for my demo environment:

When you have something similar inside your database you can select your screen on aggregation level and just insert the cube twice to your layout (one with prior period or period offset, ..., and one time with the actual period.) 

Hope it helps

regards

Alexander Kappes

dear William Le,

thanks for your request.

Do you mean the log file you enable in the reader list?

For this case the log file will be inserted in the same folder as the source file. In my sample you will find the logfile in c:\board\dataset\echo.

The filename is the same as the loadingfile with file extension .log

hope it helps

regards

Alexander Kappes

Dear Jean-Paul Baar,

thanks for your request.

Unfortunately it is not possible to export and reimport entity Templates.

They have to be performed for each dimensions from scratch and manually.

Hope it helps

regards

Alexander Kappes

Dear Jean-Paul Baar,

additional to my first post. Starting from BOARD 11 our new Transporter Tool is able to transport also Entity templates e.g. from UAT to Prod.

Never the less, exporting / importing to another Entity, like replicated or entities with the same name in different databases is still not possible.

Perhaps it helps

regards

Alexander Kappes

Dear Emma Howard,

thanks for your request.

For general the procedure you build up should work as expected from your side.

Never the less you can also do the following.

Build up temporarily cube on your source database. This one should have the same dimensions instead the version.

In your procedure you select the version to extract and first perform a dataflow to your temporarily cube.

In second step you extract your temp cube and got the wished behavior.

regards

Alexander Kappes

Dear Wahyu Nugraha,

what do you mean in detail?

Is your case to privilege users just for special screens?

If so, this can´t be done using system settings, you have to build up using User and Screen Entity inside your Database and cubes which manage the access for the users.

When you talk about capsule access and that special users should be able to open just special capsules you can e.g.  use BOARD Folder Profiles Board 10.0.3 Release Notes,

Hope it helps

regards

Alexander Kappes

Dear Julian Gomez,

this isn´t possible,

Only Stand Alone licenses can logon to different Servers with users defined as Authorized Visitors.

To get this work, the Stand Alone License has to be inserted into your BOARD Windows Client(s) at this position:

Hope it helps

regards

Alexander Kappes

Dear Malav Shelat,

only thing you can do is inserting the first field with drag and drop. The second has to be inserted "manualy".

You can write it manually into the sql field.

A little way to easy up this is using another entity (just temporarily during the configuration), inserting the second sql column into this and using (CTRL+C & CTRL + V) function.

Using this, please don´t forget to remove the additional entity when your reader configuration is finished.

Hope it helps

regards

Alexander Kappes