Best Of

Hi Egon Santoni, one option to perform the logic inside BOARD is to load both tables as they are and perform the processing via dataflow action of a procedure.

For this you need 4 cubes:

A Begin Date (Date type cube dim by Person) - populate from SQL

B End Date (Date type cube dim by Person) - populate from SQL

C Day (Date type cube dim by day only) - populate via dataflow using Day = day() function to hold date values for every day

D Active Flag (Integer cube by Day by Person)

To populate D, you need IF statement =if(and(c=>a,c=<b),1,0)

You can then multiply any anagraphic data by this ACTIVE flag mapping to have only values shown in days the Person was active, or even use the Active Flag as a filter in the layout depending on what you are trying to do.

I hope it helps!

Thanks,

Audrey

Hi Alberto,

It's certainly possible. The approach is to create an Integer type cube that you enable for data entry in a settings screen.

You would then process the data via dataflow, (c=a*b), ex:

A* Actuals (Month, GL Account, Department, Company, etc)

B Mapping cube (GL Account, P&L Report Line)

= C Report Cube (Month, GL Account, Department, Company, P&L Report line)

You might need some intermediary cubes to stage the data, but the above is the general idea. 

Hope that helps! Let me know if any questions.

Dear BOARDville Citizen, 

There are different methods to add a new element in BOARD. We often refer to these elements as "members" of an entity. You will need the help of a BOARD administrator to complete the task.

1. Create a data reader protocol to populate the entity with new products - either from a flat file or from a database connection (more here: Data Reader basic concepts)

2. Manually add the member from the entities tab (more here: Inserting, editing and deleting entity members)

3. Often for planning/forecasting purposes you may want to provide the ability for the end user to add "one-off" products - you could use a functionality Advanced Transformation Object to provide the user the ability to do this from a pager on the screen (more here: About ATO ). A poweruser in BOARD could complete this step for you.

Hope that helps!

Cheers,

Audrey

Hi Jack,

This somewhat depends on the screen.  If you have a select on the week in place the @Week will return the week being used in a Label.  If the select is NOT on the current week consider this

1)   Create a cube called "current Week" dimension by week only

2)   Create a screen with dataview using this cube and enter a 1 on the current week.  You could also setup a procedure to do this for "production".  Note only one week must be selected !

3)   On the screen you want the current month to appear add a label with a layout. The layout has the cube "current week" and below to it the "entity" "Week". The row should be week. Add a filter on the "current week" cube to show only if the value is >0.5 and lastly in the value column show "week" in the value.  

This will work I have the same for current year and current planning version in one of my models

Regards

Chris Field Head of Presales BOARD NE

HI All,

This is an issue at the Microsoft Operating System level rather than any specific application.  Currently there is no way for a 64 bit ODBC to talk to a 32 bt ODBC.  I have also had this issue at another customer.  BOARD is a 64 bit application.  This will also apply to any other tool.  The same is also true of MS SQL Server (note the post on using MS Reporting Services above).  MS SQL server is only 64 bit since SQL Server 2005 (which is now out of support by Microsoft).  The work arounds are really either upgrade the source system to a 64 bit version (I suspect that an old version of the software is in use and probably out of support by the vendor) or to export the data to a CSV/TXT format, which is usually possible and then use the BOARD ASCII data reader to import the data.  In my case the source system was upgraded to 64bit and the issue was resolved.  This is probably not the answer you wanted but don't believe there is another.

Chris

Hi All,

I tried a different approach which may work.  I downloaded from a public website a list of all post codes and the geo-coordinates.  I think loaded this to SQL Server table (but access or similar would also be fine.  In BOARD I have a the post code as an entity.  I then created a data reader to my SQL database and loaded the Coords to my Long and Lat cube.  You need to be careful of the formating of the post code but you allow to load and ignore errors as these will be postcodes that don't exist in your source.  I had several thousand to load so this worked well.  I did get some that did not match and then used a google search for the missing ones.

I was doing this for a proof of concept but may work for others.  I also did the same for a US Zip code list.