Best Of

Adam Elvin, that's a great outcome and thanks for sharing it.  You've linked the error to a domestic task that we, as analysts, are constantly involved with - housekeeping.  As such, we are all capable of falling foul of this error at some point. 

I for one would never have considered the re-installing of BOARD to rectify the error; instead, I would have completed a ticket and awaited the assistance of a superhero from BOARD SUPPORT - my own beingVasili Aravidis.  After reading your response and learning that it resolved the issue, and after all else had failed, I would now have no concerns with carrying out a re-install at an opportune moment.

Hi Kelly,

I am firstly assuming that:

1. Steps to calculate moving average have been carried out separately.
2. Moving Average values have been stored in the temp cube.
3. Temp cube values need to be transferred to the target cube against the correct devices and date of capture?

Does your procedure first select the current day dynamically before writing the contents of the temp cube to your target cube?  If not, you would be writing the new values over the top of all values and across all dates.

If what I've described is true, I am guessing that you you would need to select the date against which you wanted to store the temp values in the target cube.  Using a procedure, your process could look like this, where measures is the target cube:

A breakdown of the above 2 step procedure could then be as follows:

1. Selection

2.  Data flow 

   Block a.   Temp cube: 1D - Device

   Block b.   Target cube: 2D - Day, Device

   Dataflow: Target cube = a

HTH

Kind regards,

Paul Wyatt

Thanks for your help Bjorn. I will now raise it with the support desk.

Can I take it from your reply that the screen sizing feature is working as expected for you?

For completeness, I created a brand new capsule with a different database

   -   One screen only. 

   -   No masks

   -   No screen setup in any way

Same outcome when selecting 'Fit to page':

Image: Yellow area indicates the amount of screen lost when selecting 'Fit to page'

If Björn Reuber is getting a successful outcome with this feature but other users are able to document adverse outcomes, it should be understood under what conditions the features operate as designed.  This can only be described by BOARD Intl.

There are functional issues with this and a number of the new features of BOARD 10.3, features that were presented at BOARDville promising that developers needed only to wait for the release and not waste time fixing or mitigating functionality that has become native. 

For test script purposes, the release notes describe the expected behaviour of the new features and so it is very simple to evaluate this and the other new features.  

As I cannot switch off these features, I cannot recommend that GVA upgrade to BOARD 10.3 as we have external customers to whom we would have to explain the issues, and admit where we did not know the solutions to such platform features.

Hi Etienne. 

I explained this issue to BOARD UK on Thursday in a meeting to discuss this and other issues with 10.3.  They agreed to raise the point of display sizing with BOARD Intl and I am hopeful that a resolution will be implemented by, or in, the 10.5 release.  

I was also able to discuss:

1.  URL as a value not recognised as a URL. 

2.  Persistent top border line in a dataview object with all formatting removed. 

3.  Various other points. 

I’ll let you all know if I get any feedback. 

This is now a non-issue as dynamic web screen sizing is usable.  It does highlight a few points though.  The first is that we all interpret behaviour in different ways which leads to varying expectations and a breakdown in common understanding; I, for one, did not understand how to use the sizing tools and screen development together.  The second point is that new features should really be demonstrated by the developer and not left to interpretation by the user.

I now understand that the BOARD developer can set their 'canvas' size and that the sizing tools act in this pre-determined sizing.  Also, I now fully understand how using a mask as the controlling factor, it is possible to create uniform capsule screens and change their size globally if required.

The screen sizing feature is a very power one and allows for models to be displayed on various devices with greatly varying pixel resolutions. 

Well done BOARD Lab, you have allowed me to develop and effectively demonstrate to existing and future clients that they can be sitting on a tropical beach, ipad in hand, reviewing their property portfolios - it's a winner, seriously.

Regards,

Paul Wyatt

Hi dirk magerkord, In short, No.

I am not aware of any way a nexel configuration can be reused in a reconstructed object as changing the dataview layout will break the link to the NEXEL file.

Each Nexel configuration resides as a file in the [database].hbmp folders but a nexel config is a part of the object which gives the NEXEL config its context, not the other way round. 

A dataview/object with a nexel config can be duplicated and allow the user to select the nexel config from the saved library.  Also, the layout of a dataview containing a nexel config can be copied and pasted into a new dataview and, using the Fx menu option, allow the user to re-apply the nexel from the saved library.

Deleting and re-creating any block on any nexel configured model, however, results in breaking the link of that object to the nexel config.  Only with the original block layout can a 'new' nexel config be saved to the library either as a new config or overwriting the original one by using the same name.

NEXEL is amazing and allows for some fantastic modelling to be achieved but it really should come with a caveat: