Best Of

Hi Peter DeGregorio, 

This is not the Board Procedure Launcher syntax, it is the old one, as Federico Cazzalini mentioned above : Only database procedure can be called with this utility and must contain only "server-side" actions. but in the case of Broadcasting this is the syntax that should be used

Best regards,

Ahmed Lattali

Hi Miguel Angel Sisternas Seaton,

Thank you for your answer.

I have developed screen to enter project data and also I've defined configuration for suggested values. What I want to is:

-

to make a single data reader that reads data from different excel/csv/txt files and put data into one analyzer cube?

For example, I have data1.csv, data2.csv, data3.csv files. Both have id dimension. Each of them has fact columns like data1 has fact1 column, data2 has fact2 column and data3 has fact3 column.

I want to join all 3 files and write data into cube (with the structure id, fact1, fact2, fact3).

Is it possible?

I will be really grateful with your answer.

Hi Giles,

We also experienced a similar issue for one of our BOARD deployments (v.10.1.0) which related to the Procedure Launcher (as Federico suggested).

Are you running any BOARD procedures outside of BOARD using scheduled jobs (such as Windows Scheduler) and the BOARD Procedure Launcher?

If you are (and you are currently unable to upgrade to BOARD 10.1.3.41110 at this time) the solution provided to us from BOARD Support was as follows:

1. Download the procedurelauncher from link
2. Unzip the file
3. Change the extension from .ext to .exe
4. Replace the file in the folder C:\Program Files\Board\Board Server\Tools

This resolved the issue for that particular deployment.

If you happen to have a test environment, I would suggest doing it there first. 

Cheers,

Thomas

Hi C Tnu,

Can I ask, were you aware that you can place layouts into labels and control the output, as Dietmar Jeschkeit has suggested?  The reason I ask is that by understanding your level of experience, the community can provide more appropriate responses; you previously informed me that you were learning BOARD 11 and converting your previous models to it.  I have therefore assumed that you are familiar with common BOARD features, functions and modelling techniques and my responses are of a more technical nature.

So, assuming you are familiar with BOARD modelling, what you want to achieve is also easily achievable in BOARD but requrires the correct approach.  From what you've written, I am assuming that you want to display adhoc measures, selected by the user, or influenced by user selections?  If this is the case, My own approach is to create a 'report' layer.  Usually this is a single entity to control the output and a layout containing all relevant measures + the MASTER algorithm which displays the measure relating to the entity member selected.  The method of selection can either be manual from a selector or logically driven.

Image 1 below shows a single chart object.  The measure displayed is controlled by a selector [Chart Selection].  In this way, the x axis can will also be relevant to the measure. Whilst my example below is for a chart, it is easy to adapt for a label measure as you've outlined - I just don'ty have time to create a dedicated example, but also think that the principle is easily understood from the example below.

Using this method, a SORT on the highest to lowest is always active.  The master algorithm in the layout is used to display whatever measure has been selected.  Image 2 shows the makeup of the layout and the MASTER Algorithm used to select thte relevant metric.

IMAGE 1: Single chart object which can show any number of measures.  Note that the x axis is not fixed but is relative to the measure being displayed.  Also note that the SORT order is always High to low (or low to high is preferred).

IMAGE 2: Layout containing all measures and a MASTER algorithm block to display the selected measure.

If, on the other hand, this makes no sense or is irrelevant, I'll move along as these are clearly not the methods you're looking for...

Regards,

Paul 

Hey C Tnu

I'm not sure I fully understand your requirements as you've shown only the measure image and not the screen to put everything into context.  That said, I use several methods to 'reveal' data.  I do appreciate that you will already know and use the under-mentioned techniques individually but I hope I can demonstrate their use in a more'creative' manner to meet your need.  Also, I have an interest in being able to 'pop-out' info in this way, working around some BOARD design issues - I would love to have FLOATING DYNAMIC POP-OUT 'MEASURES' AND 'SPARKLINES' over the top of the screen layout level. 

If any of the below techniques interest you, let me know and we can discuss how to achieve what you're after and we could both learn something.  I do realise that you're trying to display a single fact/measure/kpi value but maybe these methods will include a suitable solution you can use, and I was just leaving for the weekend when I saw your post and wanted to provide you with a response?

The methods I use are:

• MASTER Selection (Image 1) - Used with multiple hierarchies where I might show PROPERTY with several LEASE records so that the user can select any of the LEASE records to reveal details.  A screen containing PROPERTY details is presented and a dataview is used to present all LEASE records; the underlying cube contains the entities PROPERTY and LEASE.  A LABEL is used which 'hides' the underlying LEASE detail dataviews if there is more than one LEASE record.  The label instructs the user to select a lease to reveal the details of it and allowing for another lease to be selected as required.
• Drillthrough (Image 2) - SQL Script pulling data directly from db.  I don't use this much as it has a few limitations.
• Drilldown (Image 3) - Horizontal to Vertical record display. I use this the most as it allows the user to go on a journey and 'tell the story'.

IMAGE 1: MASTER SELECT - Different Hierarchies .  Showing four lease records available to view which are associated to the selected PROPERTY.  FYI: This method is also used to integrate with our external 'Leverton' documents repository for the selected lease - Nice bit of BOARD versatility permitting users to access and upload docs which are not accessible to the developer and allowing for GDPR compliance where required.

IMAGE 2: DRILLTHROUGH - Used to POP-OUT additional information of a selected entity.  Useful for creating simple pop-outs or inistant datadumps.  One drawback is that the data cannot be pivoted vertically (NB: data can be presented vertically but only with a dedicated SQL script to create such a view.  This brings witht it an additional liability to maintenance and data acuracy checking when expanding or amending the bases structures.)

IMAGE 3: DRILLDOWN (multiple) from record > Horizontal > Vertical.  This is my Best Practice Drill and allows for some block formatting.  You must ensure a horizontal and vertical entity is set for this to work - a common developer oversight.

Look forward to discussing.

Regards,

Paul Wyatt