About whitby

Often when you are model building or analysing an issue, you close a tab (be it a dashboard or a module) and realise you should have kept it open. Often that then means having to go away and search for the object again.   It would be really useful if like on internet browsers like Chrome, you had the option to re-open the last closed tab: Extra bonus points if it was able to be re-opened in the state it had been closed in (with pivots, filters, or blueprint view etc. preserved) ... View more

In the New UX I would like the ability to have a simple way to group different sections of the dashboard. I am thinking of something like: - The ability to add a Top/Side/Bottom border on cards - A new 'dividing line' object that can be inserted between cards  - Colour/shading card backgrounds   A challenge for users in the new UX is understanding which cards are related on a multi-card dashboard. In the old UX we were able to overcome this by using the header 3 titles (which had an underline), or using white space. While the cards/tiles in the new UX are a step forward aesthetically, we do lose something by not being able to clearly identify one section from another. You are able to add a blank card (or line image) with no background, but this takes up too much real estate on a page (particularly when many users have smaller laptop screens).   An example of what I want to achieve is shown below:     -->      ... View more

When analysing model size, the cell count field in the module tab is very useful. However it does not tell the full story as different data types use different amounts of memory. For example a number will use ~8x as much as an integer.   The current setup works well for smaller models, but can be particularly challenging when trying to analyse the impact of large & complex models.   Please can you add the module size in bytes (B/KB/MB/GB) to the module viewer next to the cell count column to assist with analysis of module space usage.   Similarly it would also be useful on the list screen.     ... View more

When creating a module with a hierarchy dimension, if the code is used as a line item, the code will display as blank for higher level nodes in the hierarchy.    This is not the case in the list screen for example and is very disappointing for business users used to other tools who do not like the workaround of including the code in the hierarchy name.   Adding functionality that would enable aggregation would be very useful (e.g. by using a formula summary method)   Module View: List View:             ... View more